Related articles |
---|
[2 earlier articles] |
Re: When to do inline expansion salomon@silver.cs.umanitoba.ca (1993-09-20) |
Re: When to do inline expansion davidm@questor.rational.com (1993-09-20) |
Re: When to do inline expansion jfc@athena.mit.edu (1993-09-21) |
Re: When to do inline expansion jgmorris+@cs.cmu.edu (1993-09-21) |
Re: When to do inline expansion jdean@bergen.cs.washington.edu (1993-09-21) |
Re: When to do inline expansion salomon@silver.cs.umanitoba.ca (1993-09-22) |
Re: When to do inline expansion preston@dawn.cs.rice.edu (1993-09-22) |
Re: When to do inline expansion cliffc@rice.edu (1993-09-22) |
Re: When to do inline expansion rfg@netcom.com (1993-09-25) |
Re: When to do inline expansion ssimmons@convex.com (1993-09-27) |
Newsgroups: | comp.compilers |
From: | preston@dawn.cs.rice.edu (Preston Briggs) |
Keywords: | optimize |
Organization: | Rice University, Houston |
References: | 93-09-063 93-09-075 |
Date: | Wed, 22 Sep 1993 14:43:51 GMT |
jfc@athena.mit.edu (John F Carr) writes:
>Are there any commercial compilers which do not allocate a value to the
>same register over its entire live range, but instead will save it on
>the stack in those blocks where the value is live but not accessed and
>it would be benficial to let another value use that register?
Sure -- any non-global allocator does this :-)
Usually, we think of the live range splitting work of Chow and
Hennessy, which is available in the old MIPS compilers and all the
places they've migrated to (SGI, DEC, who else?). Of course,
Chaitin's allocator also meets the letter, if not the spirit, of your
specification.
Preston Briggs
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.