Re: Results for egcs-2.92.22 19981122 (gcc2 ss-980609 experimental) testsuite on i586-pc-linux-gnu

[Jeffrey A Law <law at cygnus dot com>]

  In message <87zp9apo6n.fsf@loki.wkstn.nix>you write:
  > Jeffrey A Law <law@cygnus.com> writes:
  > 
  > > I bootstrapped with -O9 and -O1 again the other afternoon.
  > > 
  > > Precisely what problems are you having
  > 
  > -O9 ICEs in stage1 with
Err, I see man more options than just -O9.  If you want us to look into these
problems in the future, you'll have to supply accurate information.   When you
do not provide this information you end up wasting everyone's time and after
a while people will just ignore you because they can not reproduce your
problems.

  > 
  > ./xgcc -B./ -B/usr/packages.bin/egcs/snapshot/i586-pc-linux-gnu/bin/ -O2   
  > -DIN_GCC    -W -Wall -W -Wall -O9 -funroll-all-loops -g -march=pentium -mcp
  > u=pentium -fomit-frame-pointer -I./include  -fPIC -g1  -DIN_LIBGCC2 -D__GCC
  > _FLOAT_NOT_NEEDED   -W -Wall -O9 -march=pentium -mcpu=pentium -fomit-frame-
  > pointer -g -D__NO_MATH_INLINES -I. -I../../egcs/gcc -I../../egcs/gcc/config
  >  -I../../egcs/gcc/../include \
  >   -c -fexceptions ../../egcs/gcc/cp/exception.cc
  > ../../egcs/gcc/cp/exception.cc: In function `void __check_eh_spec(int, cons
  > t void **)':
  > ../../egcs/gcc/cp/exception.cc:300: Internal compiler error.
  > ../../egcs/gcc/cp/exception.cc:300: Please submit a full bug report to `egc
  > s-bugs@cygnus.com'.
This must be stage2, the C++ compiler is not built in stage1.

ANd I still don't know how the stage1 compiler was built.  I've got better
things to do than figure out what you're doing to cause these problems.
Maybe someone else is willing to slog through this.  I am not.  I've got
many other things I can/should be doing.

  > You suggested earlier that this might be a loop unrolling bug. My
  > testsuite scripts are totally shagged at the moment, though, so I
  > can't really tell ;) when they come back online (later today or
  > tomorrow, I hope) I'll see if this recurs if I turn loop unrolling
  > off.
That's because you had listed it as one of your options at one point.  Then
you just started saying "-O1 and -O9" fail, without mentioning that you
were still using -funroll-loops -fomit-frame-pointer and several more options.


Jeff