On Sep 22, 2005, at 7:39 PM, Kenneth Zadeck wrote:
I will pull a patch together tomorrow. There is currently nothing
in the code for keeping the region stuff up to date as changes are
made to the cfg. For most changes this would not be hard, but for
some it is really hard.
OK. I've code (about 6 months old) to keep loop info update during
jump threading. I couldn't finish that work to keep loop info upto
date from very beginning till end at that time. But now, I am seeing
some day light, so hopefully I'll get back to it soon.
-
Devang
Daniel Berlin wrote:
On Thu, 2005-09-22 at 18:49 -0700, Devang Patel wrote:
On Sep 22, 2005, at 2:32 AM, Steven Bosscher wrote:
On Sep 22, 2005 11:25 AM, Zdenek Dvorak
<[EMAIL PROTECTED]> wrote:
4. Other ideas?
Preserving the information about loops throughout the
optimizations, and
just keeping this information attached at the loop description
would by
far be the cleanest approach -- admitedly also the one that
requires the
greatest amount of work.
Shouldn't the regions patch allow us to preserve loops quite
easily?
Any pointer to this "regions patch" ?
Thanks,
Ask kenny for a copy.
-
Devang
