Related articles |
---|
rearranging code invalidates liveness info fjh@munta.cs.mu.OZ.AU (1994-06-10) |
Re: rearranging code invalidates liveness info preston@noel.cs.rice.edu (1994-06-13) |
Re: rearranging code invalidates liveness info cliffc@noel.cs.rice.edu (1994-06-13) |
rearranging code invalidates liveness info ssimmons@convex.com (1994-06-13) |
Re: rearranging code invalidates liveness info newburn@aslan.ece.cmu.edu (1994-06-13) |
Re: rearranging code invalidates liveness info mernst@research.microsoft.com (1994-06-15) |
Re: rearranging code invalidates liveness info hbaker@netcom.com (1994-06-16) |
[2 later articles] |
Newsgroups: | comp.compilers |
From: | fjh@munta.cs.mu.OZ.AU (Fergus Henderson) |
Summary: | How do compiler writers handle this problem? |
Keywords: | optimize, question |
Organization: | Computer Science, University of Melbourne, Australia |
Date: | Fri, 10 Jun 1994 12:37:12 GMT |
I'm part of a team developing a compiler (which happens to be for a logic
programming language). We do quite a bit of analysis of the source code
before generating code. The code is annotated with the information
derived from this analysis, including liveness info, variable binding
info, variable scope info, etc.
The problem I've run into is that this organization seems to make code
reorganization for optimization purposes quite difficult, since anything
but the most trivial rearrangements will invalidate the annotations on the
code. I'm sure this problem must have been encountered by many of you
before. How do compiler writers usually handle this problem?
--
Fergus Henderson - fjh@munta.cs.mu.oz.au
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.