From: Rick Hohensee <humbubba@smarty.smart.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] partial-Plan9ification question
Date: Fri, 13 Jul 2001 14:26:35 -0400 [thread overview]
Message-ID: <200107131826.OAA09484@smarty.smart.net> (raw)
In-Reply-To: <20010713062335.4AFC3199C0@mail.cse.psu.edu> from "David Gordon Hogan" at Jul 13, 2001 02:23:32 AM
>
> > 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.
>
> ebx, esi and edi are callee save under GCC. ebp is the frame pointer, so
> that one gets preserved too (I've no idea what happens if you compile with
> -fomit-frame-pointer).
I've never had -fomit-frame-pointer break anything. I think maybe it's an
extranaeity for Pascal. Or for if you suddenly decide your GNU C is
Pascal on the fly. i.e. I don't get why it's not the default.
Thanks to replyers fore and aft of this post. Looks like my headers
question is all on me.
Rick Hohensee
>
> This means that in the Plan 9 port of GCC, the system call wrappers
> have to push these four registers, then push copies of all the arguments...
>
next prev parent reply other threads:[~2001-07-13 18:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 6:23 David Gordon Hogan
2001-07-13 18:26 ` Rick Hohensee [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 5:53 forsyth
2001-07-13 6:26 ` Mike Haertel
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=200107131826.OAA09484@smarty.smart.net \
--to=humbubba@smarty.smart.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).