http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55030
--- Comment #12 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2013-02-17 00:33:17 UTC --- (In reply to comment #10) > I'm getting back to this because I think that we should reinstate the original > patch, now that the blockage patch has been installed. *wake-up reactions* > I have run into the same issue as your original issue with a private port on > the 4.7 branch: the clobber causes the restoring of the frame pointer to be > deleted > http://gcc.gnu.org/ml/gcc-patches/2012-10/msg01172.html > Later reload allocates a stack slot to a pseudo that is set before the setjmp > and used after, but the frame pointer doesn't have a consistent value... Yup, this far I remember. > Clearly the frame pointer needs to be restored so the clobber is wrong. It > was > there because the final blockage wasn't blocking enough, but the blockage > patch > is supposed to have fixed that. I've lost track. What was "the original patch", what do you mean by "the blockage patch" (that has been installed) and I'm pretty sure there were several follow-up patches, so I can't say I'm confident about reverting something from just this subset. (To wit: if it's something that causes volatile asms to again be treated different from (other) blockages, then that's wrong, as a volatile asm is the default blockage.) Can you please a candidate (reverting?) patch gcc-patches@ *and CC me* (I'm far behind on reading gcc lists).
