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: A reload inheritance bug


On Tue, May 15, 2007 at 04:27:21PM +0100, Mark Shinwell wrote:

> Part of the reason for starting this thread was that I was concerned
> about invalidating reloads that could be re-used later.  However, it
> seems to me that in every circumstance where the reload register is a
> hard register and the value assigned to that reload register is
> different from the value held by the register during the evaluation of
> the subexpression being reloaded (as we have here with r9 <- r9 + r10),
> we must invalidate all previous reloads involving that hard register.
> I may well have encoded that logic incorrectly in the patch, though.

   I'd say try the usual testing procedure with the addition of saving away
libgcc, newlib, libiberty etc. for code size comparison. If you find any, at
least we'll be that much wiser.

-- 
Rask Ingemann Lambertsen


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