This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: target/10213: [3.4 regression] optimization problem with ix86 fast prologue with -O2 -fPIC
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, jh at suse dot cz, nobody at gcc dot gnu dot org, snyder at fnal dot gov
- Date: 15 May 2003 04:41:54 -0000
- Subject: Re: target/10213: [3.4 regression] optimization problem with ix86 fast prologue with -O2 -fPIC
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, jh at suse dot cz, nobody at gcc dot gnu dot org, snyder at fnal dot gov, gcc-gnats at gcc dot gnu dot org
Synopsis: [3.4 regression] optimization problem with ix86 fast prologue with -O2 -fPIC
State-Changed-From-To: analyzed->feedback
State-Changed-By: bangerth
State-Changed-When: Thu May 15 04:41:54 2003
State-Changed-Why:
So, Scott, what's your verdict: should it be closed? What's
the state on the 3.3 branch?
Other question: if it's "fixed" by just disabling something
(is this what you mean by "switching off") -- will we see
the problem happening again if this code patch is switched
on again by someone? Or was the code that produced the
wrong code removed altogether? If this isn't the case, then
I'd say we should keep the report, but lacking technical
insight I leave this up to you.
Thanks
W.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10213