This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Reload patch to improve 386 code
- To: crux at pool dot informatik dot rwth-aachen dot de (Bernd Schmidt)
- Subject: Re: Reload patch to improve 386 code
- From: Joern Rennecke <amylaar at cygnus dot co dot uk>
- Date: Tue, 8 Sep 1998 01:59:31 +0100 (BST)
- Cc: law at cygnus dot com, meissner at cygnus dot com, toon at moene dot indiv dot nluug dot nl, egcs at cygnus dot com
> > 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.