https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38486
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the IL issues have been resolved meanwhile (via MEM_REF introduction I
think), that we don't miscompile this is because we're good at DWIM here.
There's no way to diagnose the issue across function calls and generally
the -Wstrict-aliasing warning is frowned upon nowadays.
So WONTFIX.
