https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84528
--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- Bah, this'll be https://gcc.gnu.org/ml/gcc-patches/2017-11/msg02061.html . I hadn't realised that the -fomit-frame-pointer handling was the reason it was no longer a problem.
