Re: SPARC references

chased@Eng.Sun.COM (David Chase)
Mon, 1 Apr 91 09:29:13 PST

          From comp.compilers
Related articles
SPARC references ressler@cs.cornell.edu (1991-03-20)
Re: SPARC references salomon@ccu.umanitoba.ca (1991-03-24)
Re: SPARC references jpff@maths.bath.ac.uk (John ffitch) (1991-03-28)
Re: SPARC references salomon@ccu.umanitoba.ca (1991-03-29)
Re: SPARC references chased@Eng.Sun.COM (1991-04-01)
Re: SPARC references pardo@cs.washington.edu (1991-04-01)
Re: SPARC references torek@elf.ee.lbl.gov (1991-04-12)
| List of all articles for this month |
Newsgroups: comp.compilers
From: chased@Eng.Sun.COM (David Chase)
Keywords: SPARC, code
Organization: Compilers Central
References: <1991Mar20.222801.11711@cs.cornell.edu> <1991Mar24.222923.10183@ccu.umanitoba.ca> <1991Mar28.115715.3545@maths.bath.ac.uk> <1991Mar29.214751.3045@ccu.umanitoba.ca>
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.


David Chase
Sun
--

Post a followup to this message

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