Re: bootstrap failure of tree-ssa on armv5l-linux

[Diego Novillo <dnovillo@redhat.com>]

On Mon, 2003-05-12 at 09:01, jeroen dobbelaere wrote:
> Diego Novillo wrote:
> > On Mon, 2003-05-12 at 03:59, jeroen dobbelaere wrote:
> > 
> >>Hi,
> >>
> >>I've added the tree-ssa branch to my 'daily gcc-cvs build platform' which is based on
> >>a i80200 (xscale core, armv5l architecture) processor.
> >>
> > 
> > Thanks.
> > 
> > 
> >>Currently the bootstrap failes with following lines :
> >>
> > 
> > Hmm, this looks target-specific.  It may be bad RTL coming out of the
> > tree-ssa passes.  I doubt I can reproduce it on another target, but
> > could you post a .i file?
> > 
> > If you can reproduce this with -fdisable-simple, then the problem may
> > not be in the gimplifier nor the tree optimizers.
> 
> With -fdisable-simple, the file compiles fine, and I get :
> 
>   stage1/xgcc -Bstage1/ -B/usr/local/gcc-3.5-tree-ssa-cvs/armv5l-unknown-linux-gnu/bin/ -c   -g -O2  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Werror -fno-common -Wno-error 
> -DHAVE_CONFIG_H -DGENERATOR_FILE    -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include -I../../gcc/gcc/../libbanshee/libcompat -I../../gcc/gcc/../libbanshee -I../../gcc/gcc/../libbanshee/points-to 
> ../../gcc/gcc/genattrtab.c -o genattrtab.o -fdisable-simple
> ../../gcc/gcc/genattrtab.c:0: warning: -fdisable-simple also disables optimizations on trees
> > 
> > If you can reproduce this with -fdisable-tree-ssa, then the problem is
> > in the tree optimizers.
> 
Drat.  There's a missing 'not' in that sentence.  If you can reproduce
the problem with -fdisable-tree-ssa, the problem is *not* in the
optimizers.  It seems to be a gimplifier problem, then.

> But at the moment of the merger (2003/05/04) the mainline also had problems bootstrapping.
>
Ah, there's hope then.  I will be committing a new merge today or
tomorrow.  Please try with that when it's ready.

> Although, '-fdisable-simple' seems to work fine, so I don't know if this is related.
> 
Hmm, yeah.  I'll see if I can reproduce the problem on my end as well.


Diego.