RELOAD_OTHER bug?

[DJ Delorie]

This seems to have gotten forgotten:

> Date: Wed, 14 Dec 2005 21:12:20 -0500
> From: DJ Delorie <dj@redhat.com>
> 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