https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115966
--- Comment #2 from Filip Kastl <pheeck at gcc dot gnu.org> --- (In reply to Richard Biener from comment #1) > I think we have a few other gcc miscompiles now (but from SPEC CPU 2017), so > this one is probably related. Does -fno-strict-aliasing fix it? Just tested it, -fno-strict-aliasing doesn't help