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) |
Re: rearranging code invalidates liveness info cliffc@noel.cs.rice.edu (1994-06-16) |
Re: rearranging code invalidates liveness info daniel@quilty.stanford.edu (1994-06-21) |
Newsgroups: | comp.compilers |
From: | newburn@aslan.ece.cmu.edu (Chris Newburn) |
Keywords: | optimize |
Organization: | Electrical and Computer Engineering, Carnegie Mellon. |
References: | 94-06-070 |
Date: | Mon, 13 Jun 1994 22:35:28 GMT |
Fergus Henderson <fjh@munta.cs.mu.OZ.AU> wrote:
>[Code reorganization breaks analysis data. What to do?]
I incrementally maintain data flow info such as liveness hierarchically in
an ordered program dependence graph. As code is moved within the program,
i.e., into, out of, or past a region, data flow info can be maintained
incrementally. This incremental approach is helpful when liveness info is
required to do code motion, but the code motion affects that liveness info.
I haven't yet written this up anywhere, so I'm afraid I can't provide all
of the details.
-Chris
--
Chris J. Newburn newburn@ece.cmu.edu
Department of Electrical and Computer Engineering, Carnegie Mellon University
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.