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

--- Comment #16 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jeffrey Walton from comment #15)
> It looks like -fno-strict-aliasing cleared the crash. This is bad because I
> thought we did not violate aliasing rules.
> 
> Let me try to find it.

Well since the way -fno-strict-aliasing disables a lot of memory based
optimizations, it does not mean there is an aliasing violation. Just the
different internal representation is different later on causing other issues.

Reply via email to