This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A few SPEC95 results for the new register allocator
- To: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Subject: Re: A few SPEC95 results for the new register allocator
- From: Michael Matz <matzmich at cs dot tu-berlin dot de>
- Date: Sat, 24 Feb 2001 04:25:30 +0100 (MET)
- cc: <gcc at gcc dot gnu dot org>
Hi,
On Fri, 23 Feb 2001, Toon Moene wrote:
>
> stage1/xgcc -Bstage1/ -B/usr/snp/alphaev6-unknown-linux-gnu/bin/ -c
> -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long
> -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/.
> -I../../gcc/gcc/config -I../../gcc/gcc/../include ../../gcc/gcc/dce.c -o
> dce.o
> ../../gcc/gcc/dce.c: In function `eliminate_dead_code':
> ../../gcc/gcc/dce.c:617: Internal compiler error in gen_add2_insn, at
> optabs.c:3739
> Please submit a full bug report, with preprocessed source if
> appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
Hmm, here the stage1 compiler crashes, which is compiled with the system
compiler, so at least this can't be a miscompilation resulting from the
new reg-allocator. It still can be caused by it of course. To test this,
you can compile the above file (in the gcc dir, with the exact same
command as above), with the additional flag -fno-new-ra. If it still
crashes, it's not caused by new-RA in any way, but has other reasons (if
that's the case we might consider to merge HEAD again into new-RA, if HEAD
bootstraps on Alpha). Note, that the above only holds for the stage1
compiler. If the stage2 compiler crashes also with -fno-new-ra it can
also means, it was miscompiled by the stage1 one, but for your case it
should be a safe guess.
Ciao,
Michael.