[Bug tree-optimization/86341] Aggressive loop unrolling in gcc 7.x produces out-of-bounds index

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

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needs-bisection

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Hmm, even though we still unroll the same in GCC 8/9/10/11, we don't warn
about:
  _50 = MEM[(const int *)&t].items[3];


Though on the trunk we do the correct thing and don't unroll the loop past the
bounds and don't produce the [3] load.