[Bug middle-end/64032] [5 Regression] FAIL: gcc.dg/undefined-loop-2.c (test for warnings, line 18)

[ams at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64032

--- Comment #2 from Andrew Stubbs ams at gcc dot gnu.org ---
When I configure for powerpc-linux-gnu, undefined-loop-2.c.003t.original
contains this:

  if (((p != 0 ? (unsigned char) array1[i] != 0 : (unsigned char) array2[i] !=
0)  i = 4)  i = 99) goto D.2332; else goto D.2334;


When I configure for x86_64-linux-gnu, the same command and dump file contains
this:

  if ((p != 0 ? (signed char) array1[i] != 0 : (signed char) array2[i] != 0) 
i = 4) goto D.1837; else goto D.1839;

It looks like something has started optimizing the code really very early. This
surprises me!

[Bug middle-end/64032] [5 Regression] FAIL: gcc.dg/undefined-loop-2.c (test for warnings, line 18)

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64032

Richard Biener rguenth at gcc dot gnu.org changed:

   What|Removed |Added

 Target|hppa-unknown-linux-gnu  |hppa-unknown-linux-gnu,
   ||i?86-*-*
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2014-11-24
  Component|c   |middle-end
 CC||ams at gcc dot gnu.org
 Ever confirmed|0   |1
Summary|FAIL:   |[5 Regression] FAIL:
   |gcc.dg/undefined-loop-2.c   |gcc.dg/undefined-loop-2.c
   |(test for warnings, line|(test for warnings, line
   |18) |18)
   Target Milestone|--- |5.0

--- Comment #1 from Richard Biener rguenth at gcc dot gnu.org ---
I also see this on x86_64 with -m32.