This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RELOAD_OTHER bug?

From: Joern RENNECKE <joern dot rennecke at st dot com>
To: DJ Delorie <dj at redhat dot com>
Cc: gcc at gcc dot gnu dot org, ian at airs dot com
Date: Tue, 13 Dec 2005 19:32:18 +0000
Subject: Re: RELOAD_OTHER bug?
References: <439F14E1.8060301@st.com> <200512131911.jBDJBDhi032196@greed.delorie.com>

DJ Delorie wrote:

No, anything merged with RELOAD_OTHER has to be RELOAD_OTHER.

Why?

RELOAD_FOR_OTHER_ADDRESS only lives till the RELOAD_OTHER input reloads.

Does this mean that RELOAD_FOR_OTHER_ADDRESS reloads can never be merged with RELOAD_OTHER reloads?

Yes. But if they load the same value as a RELOAD_OTHER input, they can share the same reload register.

References:
- Re: RELOAD_OTHER bug?
  - From: Joern RENNECKE
- Re: RELOAD_OTHER bug?
  - From: DJ Delorie

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]