Path: utzoo!utgpu!water!watmath!clyde!att!alberta!ubc-cs!uw-beaver!cornell!mailrus!uflorida!haven!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.arch
Subject: Re: CISC instructions
Message-ID: <13266@mimsy.UUCP>
Date: 28 Aug 88 13:22:10 GMT
References: <13254@mimsy.UUCP> <2912@wright.mips.COM>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 18

In article <2912@wright.mips.COM> earl@mips.COM (Earl Killian) writes:
>[2.8x faster version].  You mistakenly assumed you need a frame pointer, 
>and used an argument pointer ....

Well, actually, I was thinking in terms of what I could do with PCC
and the current 4.3BSD-tahoe, without doing serious surgery.  I need
ap to make sigtramp work as is (otherwise I could just use positive
offsets from fp, a la the Tahoe); and I need fp to keep PCC happy,
and to make alloca() work (you do not expect me to force everyone
to give up GNU Emacs! :-) ).

>No registers saved is actually quite realistic, when the call protocol
>uses a mix of both callee and caller-saved registers.

Not possible `without doing serious surgery'.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris