http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52684
--- Comment #10 from davem at gcc dot gnu.org 2012-05-03 05:18:11 UTC --- Created attachment 27298 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27298 Proposed fix. It turns out to in the end be a sparc specific problem. This makes sure, in the sparc backend, that we mark the MEM_EXPR of a MEM addressable if we pass it directly into a libcall.
