Compiler error in gcc-2.95.1 on SunOS ao470 4.1.3_U1 3 sun4
Jeffrey A Law
law@cygnus.com
Wed Oct 20 22:40:00 GMT 1999
In message <199909091449.KAA08388@radar.naic.edu>you write:
> While compiling teTeX v 1.0.6 with gcc-2.95.1 freshly compiled on a
> (nolan@ao470 170) uname -a
> SunOS ao470 4.1.3_U1 3 sun4
> machine, I got a "please submit a full bug report". Here it is.
>
> It does not fail with -O2
>
> Command line:
> /pkg/gnu/bin/gcc -v --save-temps -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -O3 -c
> vftovp.c >& bug.out
>
> And the output (bug.out):
> Reading specs from /pkg/egcs/lib/gcc-lib/sparc-sun-sunos4.1.3_U1/2.95.1/spe
> cs
> gcc version 2.95.1 19990816 (release)
> /pkg/egcs/lib/gcc-lib/sparc-sun-sunos4.1.3_U1/2.95.1/cpp -lang-c -v -I. -I
> . -I.. -I./.. -D__GNUC__=2 -D__GNUC_MINOR__=95 -Dsparc -Dsun -Dunix -D__spa
> rc__ -D__sun__ -D__unix__ -D__sparc -D__sun -D__unix -Asystem(unix) -Asyste
> m(bsd) -D__OPTIMIZE__ -D__GCC_NEW_VARARGS__ -Acpu(sparc) -Amachine(sparc) -
> DHAVE_CONFIG_H vftovp.c vftovp.i
> GNU CPP version 2.95.1 19990816 (release) (sparc)
> #include "..." search starts here:
> #include <...> search starts here:
> .
> ..
> /usr/local/include
> /pkg/egcs/lib/gcc-lib/sparc-sun-sunos4.1.3_U1/2.95.1/../../../../sparc-sun
> -sunos4.1.3_U1/include
> /pkg/egcs/lib/gcc-lib/sparc-sun-sunos4.1.3_U1/2.95.1/include
> /usr/include
> End of search list.
> The following default directories have been omitted from the search path:
> /pkg/egcs/lib/gcc-lib/sparc-sun-sunos4.1.3_U1/2.95.1/include/g++
> End of omitted list.
> /pkg/egcs/lib/gcc-lib/sparc-sun-sunos4.1.3_U1/2.95.1/cc1 vftovp.i -quiet -
> dumpbase vftovp.c -O3 -version -o vftovp.s
> GNU C version 2.95.1 19990816 (release) (sparc-sun-sunos4.1.3_U1) compiled
> by GNU C version 2.95.1 19990816 (release).
> vftovp.c: In function `zoutoctal':
> vftovp.c:435: Internal compiler error in `schedule_block', at haifa-sched.c
> :6903
> Please submit a full bug report.
> See <URL: http://www.gnu.org/software/gcc/faq.html#bugreport > for instructio
> ns.
Thanks. I've been unable to reproduce this with the gcc-2.95.2 prerelease.
I don't know if that's because the bug has been fixed, or just isn't
triggering anymore.
jeff
More information about the Gcc-bugs
mailing list