>Number:         5491
>Category:       bin
>Synopsis:       gcc gets signal 11 with certain options and input files
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun May 24 13:50:00 1998
>Last-Modified:
>Originator:     Klaus Weber
>Organization:
	not organized.
>Release:        NetBSD 1.3.1
>Environment:
System: NetBSD zork.north.de 1.3.1 NetBSD 1.3.1 (ZORK) #0: Wed Apr 22 02:25:22 CEST 1998 gizmo@zork.north.de:/usr/src/sys/arch/i386/compile/ZORK i386


>Description:
During my attempts to get the last bit of speed out of xlockmore, 
I found a combination of compiler-flags and input files which makes
gcc get a signal 11 while compiling a file. This is repeatable, so
it is not a case of faulty memory or something. I don't know if it
happens on architectures other than i386.

>How-To-Repeat:
(assuming *csh:)

cd /usr/pkgsrc/x11/xlockmore
setenv CFLAGS "-O6 -fomit-frame-pointer -finline-functions -ffast-math -funroll-loops -fforce-mem -fforce-addr"
make

>Fix:
No idea.

Workaround: Omit "-funroll-loops" (for life1d.c only, all other 
files compile fine).
>Audit-Trail:
>Unformatted:
>> Checksum OK for xlockmore-4.10.tar.gz.
===>  Extracting for xlockmore-4.10
[... stuff removed ...]
cc -c -o life1d.o  -DHAVE_CONFIG_H -DDEF_FILESEARCHPATH=\"/usr/X11R6/lib/X11/app-defaults/%N%S\"  -I. -I.. -I../xlock/ -I../.. -I/usr/X11R6/include -I/usr/X11R6/include  -I/usr/X11R6/include/X11 -I/usr/X11R6/include -O6 -fomit-frame-pointer -finline-functions -ffast-math -funroll-loops -fforce-mem -fforce-addr life1d.c
cc: Internal compiler error: program cc1 got fatal signal 11
*** Error code 1

Stop.
[... stuff removed ...]