This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: split_edge, reg-stack and function.c fix
- To: Jan Hubicka <hubicka at atrey dot karlin dot mff dot cuni dot cz>
- Subject: Re: split_edge, reg-stack and function.c fix
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 04 Jan 2000 18:41:41 -0700
- cc: egcs-patches at egcs dot cygnus dot com, rth at cygnus dot com
- Reply-To: law at cygnus dot com
In message <19991217005414.A27110@atrey.karlin.mff.cuni.cz>you write:
>
> This patch is completely obsoletted by your changes and some others. Please
> ignore it.
> > > * toplev.c (rest_of_compilation): Do shorted_branches after reg
> stack.
> > I've installed this change.
> Be curefull with this.
> The new backend is not prepared for this step yet and splitting after
> reg-stack causes lossage (it was OK for old backend, because it didn't
> defined lenght attribute).
Can you please explain why? Something is rather broken if moving the
branch shortening pass to its proper place is causing the tree to stop
working.
> Would you mind to consider my small INDREG infrastructure patch? It
> basically defines the INDREG rtl construct and add necesary bits.
I've got others that I need to look at before the INDREG stuff. (like
SUBREG_BYTE).
I'd still like to see a technical explanation of why splitting after
regstack causes us to generate incorrect code.
jeff