This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/35136] [4.3 Regression] ICE caused by address calculation with loop variable when optimization is on
- From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Feb 2008 21:54:09 -0000
- Subject: [Bug middle-end/35136] [4.3 Regression] ICE caused by address calculation with loop variable when optimization is on
- References: <bug-35136-12295@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #16 from ebotcazou at gcc dot gnu dot org 2008-02-13 21:54 -------
> So, what exactly is wrong now?
Oh nothing, just the generated code. :-)
D.375_38 = (system__aux_dec__TsaB) a_3(D);
A.36 = D.375_38;
A.37_35 = (system__address *) &A.36;
ivtmp.34_32 = (unsigned int) A.37_35;
[...]
D.379_8 = (system__aux_dec__TsaB) a_3(D);
A.38 = D.379_8;
D.380_1 = &A.38 + 2;
D.381_97 = (unsigned int) D.380_1;
if (ivtmp.34_58 == D.381_97)
We compare apples (address of A.36) with orange (address of A.38).
> And what is this IVOPTs problem? ;)
It is too optimistic about addressability.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35136