Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!CS.UNC.EDU!partain
From: partain@CS.UNC.EDU (William D. Partain, msl)
Newsgroups: gnu.gcc.bug
Subject: [poirier@unc: gcc bug?]
Message-ID: <8907161741.AA02327@capella>
Date: 16 Jul 89 17:41:40 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 39


   From: poirier@unc (Dan Poirier)
   Date: Sat, 15 Jul 89 17:47:28 EDT
   Subject: gcc bug?

   Try compiling this with gcc (I did it on a Sun-3):

   main()
   {
     int *foo = {
       { 1,2 },
     };

     arf();
   }

   (I know it's not valid C, but the compiler dies with a "fatal
   signal 11", which is a segmentation fault.)

   _dan

It compiled (with errors) on a VAX.  Here are my sun3 results [gcc set
up to generate mc68010 code] (same thing on a SunOS 3.5 Sun4 [sparc]):

Script started on Sun Jul 16 13:30:51 1989
% gcc -v -c temp.c
gcc version 1.35
 /usr/local/contrib/lib/gcc-cpp -v -undef -D__GNUC__ -Dmc68000 -Dsun -Dunix -D__mc68000__ -D__sun__ -D__unix__ -Dmc68010 temp.c /tmp/cca04817.cpp
GNU CPP version 1.35
 /usr/local/contrib/lib/gcc-cc1 /tmp/cca04817.cpp -quiet -dumpbase temp.c -version -o /tmp/cca04817.s
GNU C version 1.35 (68k, MIT syntax) compiled by GNU C version 1.35.
gcc: Program cc1 got fatal signal 11.
% cat /etc/motd
Sun UNIX 4.2 Release 3.5 (SUN3CLIENT) #2: Wed May 10 12:32:05 EDT 1989
%
script done on Sun Jul 16 13:31:43 1989

Will Partain
partain@cs.unc.edu