From: khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject: Re: mingw32 2.8.0 explodes on this code
30 Jan 1998 22:13:48 -0800
Message-ID: <9801310549.AA09106.cygnus.gnu-win32@modi.xraylith.wisc.edu>
References: <3 DOT 0 DOT 2 DOT 32 DOT 19980130233120 DOT 006a2964 AT messagebox DOT com>
To: Thomas Nichols <thomas DOT nichols AT mail DOT com>
Cc: gnu-win32 AT cygnus DOT com

Thomas Nichols <thomas DOT nichols AT mail DOT com> writes:
> 
> I don't have a cygwin b18 config to test it on - is this a problem with the
> GCC code, or just with the mingw32 version?

It's a bug in gcc on all Win32 target variants.

The C compiler (cc1) is aborting due to an internal error. Here's what you
*should* see (eg., with egcs on NT -- W95 may very well not behave quite 
so well):

bomb1.c: In function `bang':
bomb1.c:19: parse error before `a'		<<<< bang0 decl.
gcc: Internal compiler error: program cc1 got fatal signal 11

I'll take a look at why cc1 is aborting.

Mumit
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".