On Sun, Sep 30, 2012 at 06:50:50PM -0400, Vladimir Makarov wrote: > But I think that LRA cpu time problem for this test can be fixed. > But I don't think I can fix it for 2 weeks. So if people believe > that current LRA behaviour on this PR is a stopper to include it > into gcc4.8 than we should postpone its inclusion until gcc4.9 when > I hope to fix it.
I think this testcase shouldn't be a show stopper for LRA inclusion into 4.8, but something to look at for stage3. I think a lot of GCC passes have scalability issues on that testcase, that is why it must be compiled with -O1 and not higher optimization options, so perhaps it would be enough to choose a faster algorithm generating worse code for the huge functions and -O1. And I agree it is primarily a bug in the generator that it creates such huge functions, that can't perform very well. Jakub