https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98582
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Ferruh YIGIT from comment #2)
> I can see the aliasing between incompatible types, but it bothers me not
> able to see what exactly goes wrong.
Anything can happen when a program triggers an UB and that UB is triggered when
the object with incompatible dynamic type is read through the unsigned short
pointer.
> And is there any side effect of the '-fno-strict-aliasing' other than
> allowing the non-standard compatible aliasing, may it cause performance
> impact because of the reduced optimization etc? If so I will go with
Of course it does have substantial performance impact, it prevents many
optimizations.
