From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] partial-Plan9ification question
Date: Thu, 12 Jul 2001 23:26:25 -0700 [thread overview]
Message-ID: <200107130626.f6D6QPC01961@ducky.net> (raw)
In-Reply-To: <20010713055804.8EB76199C0@mail.cse.psu.edu>
>the plan 9 compilers are strictly caller-saves, for all architectures. other details vary.
>on some platforms, a few useful constants are reserved in floating-point registers.
>
>gcc varies between architectures, and even from platform to platform,
>but i think even on the x86 with hardly any registers, some registers are callee-saved.
On x86 unix systems, eax, edx, and ecx are callee-saves, and the rest
are caller-saves. eax and edx are used for return values.
For AMD's forthcoming x86-64, the gcc folks actually had the luxury
of being able to invent their own convention, rather than having
to follow a convention dictated to them by existing tools and
libraries. They did some studies and ended up choosing about half
and half caller and callee saves. I think there are slightly more
caller-saves registers. They also went to some effort to pass a
few arguments in registers. The down side is their conventions
appear hairy.
Just to keep this from drifting off Plan 9 entirely: any luck on
the 8c sign extension bug?
next prev parent reply other threads:[~2001-07-13 6:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 5:53 forsyth
2001-07-13 6:26 ` Mike Haertel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-13 22:34 David Gordon Hogan
2001-07-13 19:15 David Gordon Hogan
2001-07-13 18:08 brucee
2001-07-13 18:37 ` Rick Hohensee
2001-07-13 6:39 David Gordon Hogan
2001-07-13 6:23 David Gordon Hogan
2001-07-13 18:26 ` Rick Hohensee
2001-07-12 22:16 Rick Hohensee
2001-07-12 22:18 ` Boyd Roberts
2001-07-13 1:55 ` Rick Hohensee
2001-07-12 22:08 David Gordon Hogan
2001-07-13 1:27 ` Rick Hohensee
2001-07-13 14:53 ` Douglas A. Gwyn
2001-07-13 22:18 ` Dan Cross
2001-07-14 1:21 ` Boyd Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200107130626.f6D6QPC01961@ducky.net \
--to=mike@ducky.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).