From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] partial-Plan9ification question
From: David Gordon Hogan <dhog@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-akyuhnjycyacqbwlnfcslryyou"
Message-Id: <20010713191514.1BC8B19A10@mail.cse.psu.edu>
Date: Fri, 13 Jul 2001 15:15:11 -0400
Topicbox-Message-UUID: ccffe5b2-eac9-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-akyuhnjycyacqbwlnfcslryyou
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

> 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.

I'ver never used it, so I've never had it break anything either.

My point was that I don't know whether ebp is callee-saved if
you use this option, and frankly I don't give a damn.


--upas-akyuhnjycyacqbwlnfcslryyou
Content-Type: message/rfc822
Content-Disposition: inline

Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Fri Jul 13 14:13:29 EDT 2001
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Fri Jul 13 14:13:23 EDT 2001
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.16.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id 5A28819A07; Fri, 13 Jul 2001 14:13:10 -0400 (EDT)
Received: from smarty.smart.net (smarty.smart.net [207.176.80.102])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 54FD1199E7
	for <9fans@cse.psu.edu>; Fri, 13 Jul 2001 14:12:14 -0400 (EDT)
Received: (from humbubba@localhost)
	by smarty.smart.net (8.9.1/8.9.1) id OAA09484
	for 9fans@cse.psu.edu; Fri, 13 Jul 2001 14:26:35 -0400
From: Rick Hohensee <humbubba@smarty.smart.net>
Message-Id: <200107131826.OAA09484@smarty.smart.net>
Subject: Re: [9fans] partial-Plan9ification question
To: 9fans@cse.psu.edu
In-Reply-To: <20010713062335.4AFC3199C0@mail.cse.psu.edu> from "David Gordon Hogan" at Jul 13, 2001 02:23:32 AM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.5
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Fri, 13 Jul 2001 14:26:35 -0400 (EDT)

>
> > 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...
>

--upas-akyuhnjycyacqbwlnfcslryyou--