priyanka (in 1152897369.905570.47830@75g2000cwc.googlegroups.co m)
said:

| Hi there,
|
| I want to learn about the calling convention that is adopted by the
| gcc compiler for C programs ? I need to learn about it immidiately
| for finding out the parameters passed to registers when a function
| call is made and print out the values of the parameters. Can anyone
| give me some pointers or refer to some book that would be helpful ?
| I tried searching at google but did not find any useful papers or
| reference.

Priyanka

Gcc provides an option to stop after generating assembly code (man
gcc). Make a very short program with the call of interest - and
examine the assembly code file. Warning: the convention may vary from
processor to processor.

"Skarmander" <invalid@dontmailme.comwrote in message
news:44b7ec53$0$31642$e4fe514c@news.xs4all.nl
There's no such thing as "the" ABI for a platform (in contrast to, say,
the register set) except that which is agreed upon by everyone. Unless, of
course, one reverses things and takes up the position that the platform is
*defined* by the ABI, which has its own problems.

I would say that position is the only logical one. Programs are generally
incompatible with libraries using a different ABI, and a "platform" is (in
the real world) a collection of libraries and programs, so for the platform
to be functional it must use a single ABI or provide mechanisms for code
using different ABIs to link (e.g. Win16/32 thunking).

In that sense, Solaris x86, Linux x86, and Windows x86 are all different
"platforms" even though they may be capable of running on the same hardware
and, in some rare cases, using the same application source. I doubt you'd
find too many people claiming those are all the same "platform".

I'm not sure if Linux and the BSDs use the same x86 ABI; I think they do,
but I also know they require special kernel support to run each others'
binaries (though that may be due to syscall, not pure ABI, differences).

S