|SPARC references email@example.com (1991-03-20)|
|Re: SPARC references firstname.lastname@example.org (1991-03-24)|
|Re: SPARC references email@example.com (John ffitch) (1991-03-28)|
|Re: SPARC references firstname.lastname@example.org (1991-03-29)|
|Re: SPARC references chased@Eng.Sun.COM (1991-04-01)|
|Re: SPARC references email@example.com (1991-04-01)|
|Re: SPARC references firstname.lastname@example.org (1991-04-12)|
|From:||chased@Eng.Sun.COM (David Chase)|
|References:||<1991Mar20.email@example.com> <1991Mar24.firstname.lastname@example.org> <1991Mar28.email@example.com> <1991Mar29.firstname.lastname@example.org>|
|Date:||Mon, 1 Apr 91 09:29:13 PST|
> The difficulty that I have had is in finding specific details on the
> calling conventions that the C compiler uses. I believe, for instance,
> that it will say that the caller, not the callee, is responsible for
> saving the floating-point registers.
Get your hands on a copy of the Applications Binary Interface. There
are two versions pertinent to your problems: the Generic ABI, and the
SPARC Processor Supplement. These are published by Prentice-Hall, and
describe the "AT&T System V Applications Binary Interface".
And yes, the caller is responsible for saving the floating-point registers.
Return to the
Search the comp.compilers archives again.