On Feb 27, 2005, at 7:46 PM, Giovanni Bajo wrote:
Richard showed already how his patches help on some of the benchamarks you
suggested. They also fix a regression since 3.4 was so much better in this
regard. Of course, compilation time goes up somehow because we are doing more
work now, but the compile time *regression* is probably because of something
else and is merely uncovered by Richard's patches. We also got reports from
other people saying that Richard's patches help.
I'm not sure we should hold such a patch to save a few percent of compilation
time at -O3. -O3 (compared to -O2) means "try to inline harder". Richard's
patches are doing exactly that. I'm sure who uses -O3 doesn't mind us doing
better what we are asked for. And if compilation time is critical for them,
they can still use -O2.
Also, I would like to see detailed reports of where the compilation time goes,
after the patch. I'm sure we can go blaming other optimizers (probably some of
the new ones) for the compile time regression.
I totally agree. There seems be a push back because of the compilation time
goes up but I think if we get at least -ftime-report reports for where the
compile time does increase we can at least fix or at least try to fix those
places.
-- Pinski
