Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!uunet!world!iecc!compilers-sender
From: chased@Eng.Sun.COM (David Chase)
Newsgroups: comp.compilers
Subject: Re: SPARC references
Keywords: SPARC, code
Message-ID: <9104011729.AA01572@rbbb.Eng.Sun.COM>
Date: 1 Apr 91 17:29:13 GMT
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>
Sender: compilers-sender@iecc.cambridge.ma.us
Reply-To: chased@Eng.Sun.COM (David Chase)
Organization: Compilers Central
Lines: 17
Approved: compilers@iecc.cambridge.ma.us

> 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
-- 
Send compilers articles to compilers@iecc.cambridge.ma.us or
{ima | spdcc | world}!iecc!compilers.  Meta-mail to compilers-request.