[gnu.gcc.bug] gcc 1.35 gets fatal signal 10

boetsch@infovax.informatik.tu-muenchen.dbp.de ("Ernst N. Boetsch ") (07/02/89)

Hello,

I had some problems to compile gdb-3.1 with gcc-1.35:

Machine:	VAXstation II/RC with ULTRIX V2.2 (close to BSD4.3).

Configuration:	gcc-1.35 made for Vax (config.gcc vax).
		The system include files were fixed with fixincludes.

Source:		printcmd.c of gdb-3.1 .


Compilation (long lines are split, indecated by '\' at the end of the
line):

gcc -v -I. -O -pipe -mgnu -fstrength-reduce -fcombine-regs \
	-finline-functions -c printcmd.c

gcc version 1.35
 /usr/local/lib/GNU/gcc-cpp -v -I. -undef -D__GNUC__ -Dvax -Dunix \
	-D__vax__ -D__unix__ -D__OPTIMIZE__ printcmd.c |
 /usr/local/lib/GNU/gcc-cc1 -quiet -dumpbase printcmd.c -mgnu \
	-fstrength-reduce -fcombine-regs -finline-functions -O \
	-version -o - |
 /usr/local/lib/GNU/gcc-as -o printcmd.o
GNU CPP version 1.35
GNU C version 1.35 (vax) compiled by GNU C version 1.35.

/usr/local/lib/GNU/gcc-cpp: gcc: output pipe has been closed
Program cc1 got fatal signal 10.


Hints:

A compilation without one of the options '-O' or '-finline-functions'
prevents gcc from the fatal signal.

A compilation without one of the options '-pipe', '-mgnu',
'-fstrength-reduce' or '-fcombine-regs' does gcc NOT prevent from the
fatal signal.