This is the mail archive of the
mailing list for the GCC project.
Re: GCSE store motion
- From: dewar at gnat dot com (Robert Dewar)
- To: dberlin at dberlin dot org, dewar at gnat dot com, mark at codesourcery dot com,roger at eyesopen dot com
- Cc: aj at suse dot de, davem at redhat dot com, gcc at gcc dot gnu dot org, rth at redhat dot com
- Date: Thu, 16 May 2002 07:48:38 -0400 (EDT)
- Subject: Re: GCSE store motion
> That means we shouldn't be spending much time trying to do software
> loop pipelining when compiling GCC, so the optimization shouldn't
> make compiling the compiler significantly slower.
I don't see how you conclude this. You have to do the analysis on every
loop. There will definitely be loops in GCC where the optimization is
possible, there will be loops where it is not. I would expect the
compiler to spend quite a bit of time trying to improve code for
loops in GCC. What I am saying is that I doubt that the overall
effect will be that benficial for GCC.