-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi!
DJ Delorie wrote: > This seems to have gotten forgotten: > > >>Date: Wed, 14 Dec 2005 21:12:20 -0500 >>From: DJ Delorie <[EMAIL PROTECTED]> >>CC: gcc@gcc.gnu.org, ian@airs.com > > >>It seems like the very next thing it does is generate and emit the >>reload insns via emit_reload_insns(). >> >>However, I modified my logic to check to see if the other thing we're >>merging with is also an address; if it's not, we stick with >>RELOAD_OTHER. I fiddled with the logic to look for reloads for the >>new RELOAD_FOR_OTHER_ADDRESS too, but I suspect if we find any, >>something may go wrong anyway. > > > http://gcc.gnu.org/ml/gcc/2005-12/msg00377.html > I would be *very* happy to see your patch in. I reported this problem 4 years ago (m68hc11 target) and proposed a patch: http://gcc.gnu.org/ml/gcc-patches/2001-06/msg00812.html I don't say it is best. It is just necessary for m68hc11 and I carry it for 4 years now on www.gnu-m68hc11.org. Stephane -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD0jiKNyQxO2LzKT0RAhNiAJ9Tv+V4FpQSdD/JWHHPg3L3dbTRtgCg3rEG mUsLaeZ49X5baXLs/FjqH8w= =pvnO -----END PGP SIGNATURE-----
