>
> > A split between local, marginal, and global registers would be an
> > interesting thing to do, and I can see it making the code more elegant. I
> > worry about it making things more complex, though, especially with us
> > already having multiple register types. (We'd double or triple the num
Dan --
You can also look at section 1.4.1' of
http://www-cs-faculty.stanford.edu/~knuth/fasc1.ps.gz
for another view of subroutine linkage from the upcoming TAOCP.
Regards,
-- Gregor
_
/ perl -e 'srand(-2091643526)
Dan --
[snip]
> I'll have to snag that manual next time I'm around a good bookstore. I've
> not read it as of yet, and Knuth generally has good things to say.
You can grab PDFs here:
http://link.springer.de/link/service/series/0558/tocs/t1750.htm
Of course, you can also browse around on
At 11:17 AM 10/29/2001 -0500, Gregor N. Purdy wrote:
> > > > *) The first five registers (I0-I4, S0-S4, P0-P4, N0-N4) are scratch
> > > and do
> > > > not have to be preserved by the callee
> > >
> > >Still thinking about this... We are reducing the overall number of reg
> > >copies going on by ad
Dan --
> >Looks like I'm going to have to write some real logic in jakoc
> >pretty soon...
>
> Ahhh! The horror! :-)
:)
> Seriously, the conventions are geared towards full-blown compilers with a
> reasonable register ordering module at the very least, which isn't
> unreasonable to expec
At 08:52 AM 10/29/2001 -0500, Gregor N. Purdy wrote:
>The first step I'm going to take is to start putting the arg and
>result counts on the stack, and remove the stack rotation stuff.
Leave the rotate opcode, though. That might come in handy for the
Forth/Scheme/Postscript folks, once we have t
At 08:43 AM 10/29/2001 -0500, Gregor N. Purdy wrote:
>Dan --
>
>On Fri, 2001-10-26 at 16:38, Dan Sugalski wrote:
> > Okay, here are the conventions.
>
>Looks like I'm going to have to write some real logic in jakoc
>pretty soon...
Ahhh! The horror! :-)
Seriously, the conventions are geared t
Sam --
> > Okay, here are the conventions.
>
> Great. Anyone want to offer up some examples or should I just wait for
> Jako support to see this in action?
I'll be working on making jakoc support the convention, but it may
take a while with my day job duties as they are. If I can get it in
qui
Dan --
On Fri, 2001-10-26 at 16:38, Dan Sugalski wrote:
> Okay, here are the conventions.
Looks like I'm going to have to write some real logic in jakoc
pretty soon...
> *) The callee is responsible for saving and restoring non-scratch registers
Nice for callee since if its work fits into five
On Fri, 26 Oct 2001, Dan Sugalski wrote:
> Okay, here are the conventions.
Great. Anyone want to offer up some examples or should I just wait for
Jako support to see this in action?
-sam
Okay, here are the conventions.
*) The callee is responsible for saving and restoring non-scratch registers
*) The first five registers (I0-I4, S0-S4, P0-P4, N0-N4) are scratch and do
not have to be preserved by the callee
*) In *ALL* cases where the stack is used, things are put on the stack in
11 matches
Mail list logo
