Path: utzoo!attcan!uunet!lll-winken!ames!think!bloom-beacon!CSRI.TORONTO.EDU!moraes
From: moraes@CSRI.TORONTO.EDU (Mark Moraes)
Newsgroups: comp.windows.x
Subject: Re: gcc-1.33
Message-ID: <8902150000.AA02071@baldwin.csri.toronto.edu>
Date: 15 Feb 89 00:00:30 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 18

We weren't able to compile the X server (fixes 1-7) and Purdue2.1 with
gcc-1.33. We haven't tried the rest (nor are we likely to)

gcc options: -O -traditional -DPURDUE

gcc-cc1 gets signal 11 and dumps core on 
	server/dix/{colormap.c,gc.c,main.c,swapreq.c,window.c},
	server/ddx/mi/{misetclip.c,mibitblt.c,miexpose.c,mibstore.c},
	server/ddx/{mfbfillrct.c, mfbline.c}

(Someone here tried it on a uVax3200, and got the following results:

>  gcc 1.33 -traditional -O dumps core on
>         server/dix/{colormap.c,gc.c,main.c,swaprep.c,window.c}
>         server/ddx/mfb/{mfbfillrct.c,mfbline.c}
>         server/ddx/dex/qdss/qdspans.c

We're staying with 1.30 till the dust settles...