https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69368
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |INVALID
--- Comment #25 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to alalaw01 from comment #23)
> Well, this one is not fixed by -fno-aggressive-loop-optimizations.
No, that just disabled one symptom of the issue at that point in time. Fixing
the issue also fixes this occurance (well, I hope so ;))
