Re: x86-64 and calling conventions

Boleslaw Ciesielski <bolek-compilers@curl.com>
Fri, 23 May 2008 12:05:14 -0400

          From comp.compilers
Related articles
[9 earlier articles]
Re: x86-64 and calling conventions vidar.hokstad@gmail.com (Vidar Hokstad) (2008-05-14)
Re: x86-64 and calling conventions james.harris.1@googlemail.com (James Harris) (2008-05-14)
Re: x86-64 and calling conventions cr88192@hotmail.com (cr88192) (2008-05-15)
Re: x86-64 and calling conventions cr88192@hotmail.com (cr88192) (2008-05-15)
Re: x86-64 and calling conventions bc@freeuk.com (Bart) (2008-05-14)
Re: x86-64 and calling conventions cr88192@hotmail.com (cr88192) (2008-05-15)
Re: x86-64 and calling conventions bolek-compilers@curl.com (Boleslaw Ciesielski) (2008-05-23)
Re: x86-64 and calling conventions gah@ugcs.caltech.edu (glen herrmannsfeldt) (2008-05-29)
| List of all articles for this month |
From: Boleslaw Ciesielski <bolek-compilers@curl.com>
Newsgroups: comp.compilers
Date: Fri, 23 May 2008 12:05:14 -0400
Organization: Aioe.org NNTP Server
References: 08-05-031 08-05-043 08-05-048
Keywords: code
Posted-Date: 24 May 2008 16:54:04 EDT

glen herrmannsfeldt wrote:
> As far as passing arguments in registers, there is at least one
> convention (possibly SPARC, but I am not sure now) where some are
> passed in registers, but stack space is still reserved for them. The
> called routine can then store them into the stack. As some number of
> words are kept in the registers, in some cases a double variable will
> be half in a register and half on the stack. Storing to the stack is
> a convenient way to get the two back together again.


This is the case for 32-bit PowerPC.


Bolek


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.