https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80968
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |sparc*-*-*
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-06-04
CC| |ebotcazou at gcc dot gnu.org
Summary|[SPARC] Stack frame |stack frame reference
|reference allowed in delay |allowed in delay slot of
|slot of return instruction. |return instruction
Ever confirmed|0 |1
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Seems like we need something like stack tie pattern like other
> backends use to block code movement like this, and emit it right
> before the epilogue sequence.
The stack tie approach is a recipe for disaster though, see the slew of bugs in
the PowerPC back-end over the past decade; I'd rather emit a frame_blockage.
