http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51471
--- Comment #6 from Mikael Pettersson <mikpe at it dot uu.se> 2011-12-12 13:10:33 UTC --- (In reply to comment #5) > So my question is: what is the mechanism that should prevent epilogue insns > from being moved to before the epilogue? A full compiler barrier? See PR38644 for an epilogue scheduling bug on ARM Thumb-1 that got fixed by prefixing the epilogue with a barrier. That PR also refers to an older PowerPC bug that was fixed in a similar way.