Seth Kurtzberg wrote: Here are the bug reports: http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=WAITING&bug_status=SUSPENDED&field0-0-0=product&type0-0-0=substring&value0-0-0=internal&field0-0-1=component&type0-0-1=substring&value0-0-1=internal&field0-0-2=short_desc&type0-0-2=substring&value0-0-2=internal&field0-0-3=status_whiteboard&type0-0-3=substring&value0-0-3=internal&field1-0-0=product&type1-0-0=substring&value1-0-0=compiler&field1-0-1=component&type1-0-1=substring&value1-0-1=compiler&field1-0-2=short_desc&type1-0-2=substring&value1-0-2=compiler&field1-0-3=status_whiteboard&type1-0-3=substring&value1-0-3=compiler&field2-0-0=product&type2-0-0=substring&value2-0-0=error&field2-0-1=component&type2-0-1=substring&value2-0-1=error&field2-0-2=short_desc&type2-0-2=substring&value2-0-2=error&field2-0-3=status_whiteboard&type2-0-3=substring&value2-0-3=error There are probably more; I don't have time to search it complete. The bugs on that page should be sufficient to show that it is not a hardware problem and it is a known problem. I have seven machines here. I've tried using 5 to investigate this. It is simply not credible that I have five machines that work perfectly (and run Haskell just fine) that all have the problem. Pointing the finger at hardware here is not the way to solve the problem.

Simon Marlow wrote:

...

On 17 February 2005 12:05, Seth Kurtzberg wrote:

...

I'm not positive about 2.95, but I know that on 3.x it crashes in different places, and even compiling different source files. With each 3.x release, they fix some of them, but others pop up to take their place. Clearly the gcc people don't know what's going on.

Are you sure this isn't a hardware problem on your system? gcc crashing randomly is usually an indicator of bad memory or similar.

Cheers, Simon

I reproduced it on forty machines, all sparc ultras. I've reproduced it on at least 10 linux boxes, two BSD boxes, and the thread started with the problem on freeBSD. It isn't hard to find the error on a zillion pages. For example:

For example: http://sources.redhat.com/ml/cygwin/1999-03/msg00083.html http://www.cygwin.com/ml/cygwin/2002-01/msg00611.html http://www.winehq.org/hypermail/wine-users/2000/12/0498.html

Some of these believe the error occrs on cc1 after it receives an error six.

I'm amazed that you haven't seen it. That's very unusual for gcc 3.x. You've been lucky.

...

_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

!DSPAM:4214950a120962022396072!