https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187
--- Comment #21 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- I've finally managed to reproduce the test failure (someone has turned off emu128 in the sources I have). Rebuilding the failing test with -fno-strict-aliasing causes the test to pass. That strongly suggests (though doesn't prove) this is a problem in the sources with aliasing violations, rather than a bug in GCC. Aliasing problems can be very hit-and-miss because the rules give more freedom to the compiler to move instructions around. Indeed disabling the instruction scheduler passes also causes the test to pass.
