https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109585
--- Comment #9 from Hector Martin <hector at marcansoft dot com> --- Yes, a strict aliasing violation could explain the behavior of the optimizer here... but given all the types are identical and there is no casting going on, clearly there is no strict aliasing violation.
