[Bug target/32523] disastrous scheduling for POWER5

["whaley at cs dot utsa.edu" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32523

--- Comment #10 from R. Clint Whaley <whaley at cs dot utsa.edu> 2010-09-29 22:22:22 UTC ---
>Out of curiosity, any benchmark updates on more recent releases?

Nope, after several rough experiences I've stopped reporting gcc bugs and
problems.  It usually takes weeks of my time, and I think only once or twice
has the problem been fixed because of my report, which is typically reported as
invalid by Pinski right up until it is fixed.  Usually the problem gets fixed
accidentally by other updates if it is ever fixed at all.

I've started to just rewrite things to ameliorate gcc problems.  I'll only
report problems if I can't get anything workable with this approach, since
rewriting whole code generators is faster than getting anyone here to confirm,
much less fix gcc problems.  I've largely insulated myself from all the gcc
performance regressions that used to cripple my library by extensive use of
assembly, which allows me to help my users even while gcc remains terribly
slow.

I don't think I'm the only developer who has been forced to take this path.

Cheers,
Clint