https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98582
--- Comment #2 from Ferruh YIGIT <ferruh.yigit at intel dot com> --- Thanks Jakup, I confirm the 'may_alias' attribute is doing the trick. -fno-strict-aliasing was already confirmed. I can see the aliasing between incompatible types, but it bothers me not able to see what exactly goes wrong. Anyway, if there is no problem with the compiler this defect can get be closed. 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 'may_alias' attribute in a reduced scope. Thanks again, ferruh
