https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70886 --- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- It's an issue in the speculative machinery of the scheduler but fortunately easy to fix once you pinpointed it...