https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97073
--- Comment #5 from Franz Sirl <sirl at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #3) > This broke in between r102000 (still good) and r104000 (already > miscompiled), so I don't believe that 6.3.1 worked. Hmm, maybe something in 6.3.1 is masking the bug? Yesterday I used "gcc version 6.3.1 20170216 (Red Hat 6.3.1-3) (GCC)" from devtoolset-6-gcc-6.3.1-3.1.el7.x86_64 to try. But in the meantime I built 6.5.0 myself and surely enough it shows the bug too?