https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47192
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2016-11-17
Ever confirmed|0 |1
--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
This is latent on the trunk, but that's only because the trunk IPA analysis has
gotten stronger and as a result it eventually is able to get rid of the
assignment that was sunk after the stack deallocation.
THe standard way to fix this is to emit scheduling barriers before cutting back
the stack in the epilogue. I'll take care of it.
