This is the mail archive of the
mailing list for the GCC project.
Re: Updating the CFG on the fly?
- To: law at cygnus dot com
- Subject: Re: Updating the CFG on the fly?
- From: Michael Hayes <m dot hayes at elec dot canterbury dot ac dot nz>
- Date: Tue, 09 Nov 1999 16:18:44 +1300 (NZDT)
- Cc: gcc at gcc dot gnu dot org
- References: <"14375.27751.463360.981973"@ongaonga.elec.canterbury.ac.nz><2316.942112467@upchuck>
Jeffrey A Law writes:
> 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.
I agree. Many of the common loop operations could be markedly
improved with a CFG.
Speaking of loop optimisations; were the low overhead loop patches I
submitted many months ago ever reviewed?