[Bug middle-end/109967] [12/13/14/15 Regression] Wrong code at -O2 on x86_64-linux-gnu

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=111422
   Target Milestone|12.5                        |11.5
         Resolution|---                         |FIXED

--- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This was fixed by the same patch which fixed PR 111422.

  ivtmp.19_7 = (unsigned long) &g;
...


  <bb 4> [local count: 89482957]:
  g ={v} {CLOBBER(eol)};
  _51 = e_16 + -1;
  f[_51] = 1;

  <bb 5> [local count: 447307436]:
  # d_36 = PHI <d_25(5), 48(4)>
  # e_37 = PHI <e_26(5), 0(4)>
  # ivtmp.14_28 = PHI <ivtmp.14_24(5), ivtmp.19_7(4)>
...


(same BB):
  # ivtmp.14_28 = PHI <ivtmp.14_24(5), ivtmp.19_7(4)>
...
  MEM[(char *)_55] = _3;


So we now know that g is alive at the same time f is alive so we know they
conflict.