Related articles |
---|
[4 earlier articles] |
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: | rfg@netcom.com (Ronald F. Guilmette) |
Keywords: | optimize |
Organization: | Compilers Central |
References: | 93-09-063 93-09-102 |
Date: | Sat, 25 Sep 1993 04:40:37 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?
preston@dawn.cs.rice.edu (Preston Briggs) writes:
>Sure -- any non-global allocator does this :-) ...
Well... since we're on the subject... I just can't resist getting in a
plug for my favorite symbolic debugging information format.
To folks building compilers which use techniques such as those described
above: Please ask yourself "How are my users going to symbolically debug
optimized code even in those cases where reasonably sophisticated register
allocation techniques have been employed?"
I think there is really only one answer... DWARF (version 2).
(I would be happy to provide the latest industry review draft of the DWARF
V2 spec to anyone who would like a copy. Just ask.)
--
-- Ronald F. Guilmette ------------------------------------------------------
------ domain address: rfg@netcom.com ---------------------------------------
------ uucp address: ...!uunet!netcom.com!rfg -------------------------------
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.