[Bug c++/30567] -fPIC -O3 optimizer bug (32-bit target only)
rwgk at yahoo dot com
gcc-bugzilla@gcc.gnu.org
Sun Feb 11 05:30:00 GMT 2007
------- Comment #6 from rwgk at yahoo dot com 2007-02-11 05:30 -------
I immediately believe that Andrew's and Wolfgang's findings are accurate, but I
never claimed that the mainline has a problem. I never even tried it.
My interest it to make sure that our code works with any new gcc release, since
that's what the OS makers pick up, and then we are stuck with the remaining
bugs for 5+ years.
It looks like a gcc 4.2 release is imminent, therefore I'm testing with the
corresponding branch.
>From other bug reports I know that you have a "regression hunt" procedure. Is
there any way I can submit my reproducer to the hunter? We have a fairly small
time bracket already, given by Andrew's 4.2 test and the day this bug was
opened. Therefore it would seem straightforward to find the checkin which
caused the problem.
I'll repeat my test with the current 4.2 branch and post my results here.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30567
More information about the Gcc-bugs
mailing list