This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Updating the CFG on the fly?
- To: Michael Hayes <m dot hayes at elec dot canterbury dot ac dot nz>
- Subject: Re: Updating the CFG on the fly?
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Mon, 08 Nov 1999 18:54:27 -0700
- cc: Joern Rennecke <amylaar at cygnus dot co dot uk>, gcc at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <14375.27751.463360.981973@ongaonga.elec.canterbury.ac.nz>you writ
e:
> > If you want to do this at loop optimization time, there isn't any CFG
> > information available in the first place.
>
> In my patches there is ;-)
Hell, we've had cfg's before loop for 2 years. Joern needs to read more
code :-)
Even if we didn't have a cfg before loop, there's nothing that prevents us
from building one. Using a cfg to drive the loop optimizer is really the
right way to go. There's *sooo* many things in loop.c that can be cleaned
up by using a cfg.
jeff