http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43653
--- Comment #11 from Jeffrey A. Law <law at redhat dot com> 2011-02-16 04:03:41 UTC --- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/15/11 15:42, ubizjak at gmail dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43653 > > --- Comment #10 from Uros Bizjak <ubizjak at gmail dot com> 2011-02-15 > 22:41:40 UTC --- > (In reply to comment #9) >> I think an x86 maintainer is going to need to take a look at this. > >> Which simply isn't going to work and it's all downhill from there, including >> a >> surprise secondary memory allocation which ultimately triggers the ICE. >> >> I was able to hack things to work by enabling a secondary reload when copying >> (plus (sp) (whatever)) into SSE_REGS, but that may not be the best solution. >> Someone with more x86 internal knowledge should look at this. > > Hm, indeed. SSE can't handle non-vector PLUS insn, so reload needs a bit of > help. It's unfortunate that reload decides to reload the constant offset, but I suspect this kind of thing is exceedingly rare. I'll let you own taking care of the PR since you've got a patch :-) jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNW0yQAAoJEBRtltQi2kC7VJsH/isQ/CjWMiBfrNea5JEqF6Hw rc955z1QyN4584IfL2Vcl1KTwvMr5zy7FJTiWbybl812a24V5b7lFwGlgDmag3/6 59XY1RdEH4j+JLYuT+bEu3IBL4orqNZSHMxDRAqzeYGbzLj16KVJeS1+cNQV4iV5 foXZGrZ+1jr4saqpBCkpA0ecid5a4eX8vtMv2EmGWnW7LW/fy2w8casgn24iGio+ 0HdMn8gBQuTGknU/u7yLf0ArS9/UBlrk8iE3VM9ssgz4oD4w3BJt0J5VMlBaqCpQ G8BgZkfrmVCAvYcEiHpa6Cj30OmR3VeWN9IDu+jUWiZhSOluo5EDIxWCU8S1FBU= =7vqY -----END PGP SIGNATURE-----
