------- Comment #12 from ian at airs dot com 2009-02-10 19:56 ------- I didn't get around to commenting on the patch; I'll just note that it is conservative. We don't have to block every instruction, just those which use memory.
Do we have to worry about the function epilogue? I don't see any reason why the scheduler would move any of the pop instructions ahead of something which references off of %rbp. But I also don't see anything which explicitly prevents that from happening. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39118
