Related articles |
---|
Caller/Callee saved Registers pmagun@iiic.ethz.ch (1994-03-14) |
Re: Caller/Callee saved Registers preston@noel.cs.rice.edu (1994-03-21) |
Re: Caller/Callee saved Registers pardo@cs.washington.edu (1994-03-22) |
Re: Caller/Callee saved Registers hbaker@netcom.com (1994-03-22) |
Caller/Callee saved Registers ssimmons@convex.com (1994-03-22) |
Re: Caller/Callee saved Registers paulb@travis.csd.harris.com (1994-03-22) |
Re: Caller/Callee saved Registers cliffc@noel.cs.rice.edu (1994-03-22) |
Re: Caller/Callee saved Registers alk@et.msc.edu (1994-03-23) |
Re: Caller/Callee saved Registers bart@cs.uoregon.edu (1994-03-23) |
Re: Caller/Callee saved Registers robertsw@agcs.com (1994-03-23) |
Re: Caller/Callee saved Registers Peter-Lawrence.Montgomery@cwi.nl (1994-03-24) |
Re: Caller/Callee saved Registers pdp8@ai.mit.edu (1994-03-24) |
Re: Caller/Callee saved Registers ghiya@flo.cs.mcgill.ca (1994-03-24) |
Re: Caller/Callee saved Registers paulb@travis.csd.harris.com (1994-03-24) |
[22 later articles] |
Newsgroups: | comp.compilers |
From: | alk@et.msc.edu (Anthony L. Kimball) |
Keywords: | registers, design |
Organization: | Compilers Central |
References: | 94-03-054 94-03-087 |
Date: | Wed, 23 Mar 1994 07:49:37 GMT |
Henry G. Baker (hbaker@netcom.com) wrote:
: ...one is then left with the uneasy
: feeling that any architecture which requires these sorts of heroics can't
: be the right thing.
Contra M. Beusterien, I feel it is an architectural issue in as
much as it is a problem most appropriately solved by throwing
hardware at it: The obvious architectural solution seems to be for
the caller to set a use mask, for the callee to set another
use mask, and for the processor to do a save of the intersection,
with special-purpose logic. Anything like this out there?
-- Anthony L Kimball -- alk@think.com, alk@msc.edu, {uunet,harvard}!think!alk
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.