From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joern Rennecke <amylaar@cygnus.co.uk>
To: crux@pool.informatik.rwth-aachen.de (Bernd Schmidt)
Cc: law@cygnus.com, meissner@cygnus.com, toon@moene.indiv.nluug.nl, egcs@cygnus.com
Subject: Re: Reload patch to improve 386 code
Date: Mon, 07 Sep 1998 19:09:00 -0000
Message-id: <199809080059.BAA01948@phal.cygnus.co.uk>
References: <Pine.GSO.4.02A.9809071547250.23612-100000@matlock.informatik.rwth-aachen.de>
X-SW-Source: 1998-09/msg00396.html

> > Then again inheritance happens just before we start emitting the
> > reload insns themselves, so maybe it doesn't conflict with your code.
> 
> It really shouldn't. Inheritance only looks at the insns that reload is
> already done with, and the one currently being processed.  For those
> which reload has completed, the register life information calculated by
> my patch is never referenced again, so the inheritance code can do
> whatever it wants to them.

You'll have to add some code to tell the inheritance code when a reload
register becomes unavailable where it becomes used by a pseudo.