This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Loop optimizer issues
- From: David Edelsohn <dje at watson dot ibm dot com>
- To: "S. Bosscher" <S dot Bosscher at student dot tudelft dot nl>
- Cc: "'Zdenek Dvorak '" <rakdver at atrey dot karlin dot mff dot cuni dot cz>, "'Richard Henderson '" <rth at redhat dot com>, "'Geoff Keating '" <geoffk at geoffk dot org>, "'Diego Novillo '" <dnovillo at redhat dot com>, "'Jason Merrill '" <jason at redhat dot com>, "'Jan Hubicka '" <jh at suse dot cz>, "'Daniel Berlin '" <dberlin at dberlin dot org>, "'pop at gauvain dot u-strasbg dot fr '" <pop at gauvain dot u-strasbg dot fr>, "'gcc at gcc dot gnu dot org '" <gcc at gcc dot gnu dot org>
- Date: Wed, 02 Jul 2003 18:07:40 -0400
- Subject: Re: Loop optimizer issues
>>>>> S Bosscher writes:
Steven> Well, surely some loop optimizers will still be necessary on RTL even with
Steven> tree-ssa, don't you think?
Please read the full context of the thread:
"but surely the code motion I'm concerned with will at least partially be
done on tree-ssa (as loop invariant motion or pre or perhaps both)."
"... ust do these high-level motions on ast-level when they are not
represented in this ugly way (and either do only simpler pass on rtl, or
don't do it there at all, depending on what will turn to be more
practical)."
Yes, RTL will have a simple loop optimizer, but not the
optimizations for which Zdenek wants to assume the absence of LIBCALLs.
David