This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problem with the special live analyzer in global alloc
- From: Andreas Krebbel <krebbel1 at de dot ibm dot com>
- To: Daniel Berlin <dberlin at dberlin dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 23 Aug 2005 16:28:54 +0200
- Subject: Re: Problem with the special live analyzer in global alloc
- References: <20050816135150.GA3617@de.ibm.com> <1124201649.18266.32.camel@MAMBA>
Hello,
sorry for the late answer.
> Vlad promised to update it to use df.c once it wasn't "1% slower", which
> would make it easily reusable elsewhere, but never did.
> Of course, you could reuse it without that, but then someone will
> invariably come along and mess with it.
Ok I understand that implementing the special lifeness analyzers in global alloc
using the df.c framework would ease reusing it somewhere else. But my question
was more basic.
So do you agree that using one lifeness analyzer for checking what
an optimizer step has done based on a second lifeness analyzers output
is wrong? If so what is the way to fix this? Going back to the normal analyzer to
be used in global alloc would make global alloc creating worse code. But on the other hand
using the global alloc lifeness analyzer everywhere else would be a change
which nobody would agree with in the current development stage.
Because this is a regression from 4.0 to 4.1 this should be fixed as soon as possible.
Bye,
-Andreas-