optimization/10030: gcc 3.2(.1) produces broken code with -O2, but not -O

[ljrittle@gcc.gnu.org]

Synopsis: gcc 3.2(.1) produces broken code with -O2, but not -O

Responsible-Changed-From-To: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Wed Mar 26 10:22:56 2003
Responsible-Changed-Why:
    Mine.  (I lowered the severity: Anything so nebulous with a posted workaround is, by default, not critical!)
State-Changed-From-To: feedback->closed
State-Changed-By: ljrittle
State-Changed-When: Wed Mar 26 10:22:56 2003
State-Changed-Why:
    9 times out of 10, we never hear from these people again.  Please just close ill-formed reports that refer to mega-packages...
    
    General Notes: A compiled program crashing at -O2 but not -O
    does not imply a compiler bug.  This is why someone (you) will
    need to produce a small test case.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10030