|compiling for mips environment firstname.lastname@example.org (simon) (1999-06-27)|
|Re: compiling for mips environment email@example.com (Zalman Stern) (1999-06-29)|
|Re: compiling for mips environment firstname.lastname@example.org (James Jones) (1999-06-29)|
|Re: compiling for mips environment email@example.com (Chris Dodd) (1999-06-29)|
|Re: compiling for mips environment firstname.lastname@example.org (Matt Postiff) (1999-07-01)|
|Re: compiling for mips environment email@example.com (Michael Meissner) (1999-07-11)|
|From:||Matt Postiff <firstname.lastname@example.org>|
|Date:||1 Jul 1999 15:02:26 -0400|
|Organization:||University of Michigan EECS|
|References:||99-06-086 99-06-110 <Pine.GSO.email@example.com>|
> 1. Why reserve stack space for arguments that are being passed in
Support of vararg functions is the primary utility of the 16-byte
reserved space as was already pointed out. These "home locations", as
they are called in the SYSV ABI, are also convenient when you need to
dump a parameter to a memory location because it's address is
taken. For example:
void main(int argc)
foo(&argc); <--- causes store of $4 into first reserved location
The ABI specs at http://www.sco.com/developer/devspecs/ are helpful.
Float arguments can be passed in $f12 and $f14 according to that spec
if they are the first one or two arguments to a non-vararg function.
Return to the
Search the comp.compilers archives again.