https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111583
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
A conservative fix would be to make sure the memory accesses for the
memset/memcpy recognition are before the loop exit. Note since -Os disables
loop header copying in most cases this will remove quite a bit of memset/memcpy
loop detection there. The alternative would be to guard the calls.
