Path: utzoo!utgpu!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!claris!apple!baum
From: baum@Apple.COM (Allen J. Baum)
Newsgroups: comp.arch
Subject: Re: register save/restore
Message-ID: <19914@apple.Apple.COM>
Date: 3 Nov 88 18:34:25 GMT
References: <3300037@m.cs.uiuc.edu> <5938@killer.DALLAS.TX.US> <7580@aw.sei.cmu.edu>
Reply-To: baum@apple.UUCP (Allen Baum)
Organization: Apple Computer, Inc.
Lines: 20

[]
>In article <7580@aw.sei.cmu.edu> firth@bd.sei.cmu.edu (Robert Firth) writes:
.
.
>F. Possibly Offensive Remark
>
>I agree with Henry, that procedure calling protocols need to be thought
>afresh for each fresh machine.  Unfortunately, very few compiler shops
>seem prepared to do this.  I see over and again the model of a closed,
>downward-growing stack; caller pushes parameters; callee saves registers
>and allocates local space.  One can do better than this by a factor of
>two or three, on almost any machine I know, with a different model more
>amenable to local optimisation.

Would you care to elaborate on how to gain a factor of two or three?
I'd like to see an example or two..

--
		  baum@apple.com		(408)974-3385
{decwrl,hplabs}!amdahl!apple!baum