This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RELOAD_OTHER bug?
- From: DJ Delorie <dj at redhat dot com>
- To: joern dot rennecke at st dot com, gcc at gcc dot gnu dot org, ian at airs dot com
- Date: Thu, 19 Jan 2006 20:25:19 -0500
- Subject: Re: RELOAD_OTHER bug?
- References: <439F14E1.8060301@st.com> <200512131911.jBDJBDhi032196@greed.delorie.com> <439F21C2.8000004@st.com> <200512132050.jBDKoNtZ001256@greed.delorie.com> <439F3976.4050801@st.com> <200512150212.jBF2CKgH020537@greed.delorie.com>
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