From owner-freebsd-current  Mon Dec 20  8:53:45 1999
Delivered-To: freebsd-current@freebsd.org
Received: from lamb.sas.com (lamb.sas.com [192.35.83.8])
	by hub.freebsd.org (Postfix) with ESMTP id 3791615293
	for <freebsd-current@freebsd.org>; Mon, 20 Dec 1999 08:53:36 -0800 (PST)
	(envelope-from jwd@unx.sas.com)
Received: from mozart (mozart.unx.sas.com [192.58.184.28])
	by lamb.sas.com (8.9.3/8.9.1) with SMTP id LAA03334;
	Mon, 20 Dec 1999 11:53:01 -0500 (EST)
Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
	id AA18209; Mon, 20 Dec 1999 11:52:31 -0500
Received: (from jwd@localhost)
	by bb01f39.unx.sas.com (8.9.1/8.9.1) id LAA01812;
	Mon, 20 Dec 1999 11:52:31 -0500 (EST)
	(envelope-from jwd)
From: "John W. DeBoskey" <jwd@unx.sas.com>
Message-Id: <199912201652.LAA01812@bb01f39.unx.sas.com>
Subject: Re: cc taking a signal 11
In-Reply-To: <199912201637.LAA81110@lakes.dignus.com> from Thomas David Rivers at "Dec 20, 1999 11:37:43 am"
To: rivers@dignus.com (Thomas David Rivers),
	freebsd-current@freebsd.org
Date: Mon, 20 Dec 1999 11:52:31 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > 
> > Hi,
> > 
> >    While I'm at it, a co-worker gave this one to me earlier today.
> > 
> >    cc: Internal compiler error: program cc1 got fatal signal 11
> > 
> >    4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
> > 
> > 
> > 
> > FreeBSD(root)/tmp %cc -v
> > Using builtin specs.
> > gcc version 2.95.2 19991024 (release)
> > 
> > FreeBSD(root)/tmp %cc -O foo.c -o foo.o -c
> > cc: Internal compiler error: program cc1 got fatal signal 11
> > 
> > 
> > 
> > static void getsig11(parfree,dbl,lambda)
> >  long parfree;
> >  double *dbl;
> >  double *lambda;
> > {
> >     long i, j;
> >     j = -1;
> >     for(i = 0; i < parfree; i++)  {
> >        j += i+1;
> >        dbl[j] *= (1.0 + *lambda);
> >        }
> >     return;
> > }
> > 
> > 
> >    Yes, the algorithm looks funny, but is correct. The program will
> > compile correctly if the 'j += i+1;' is changed to 'j = i+1;' or if
> > the variable 'lambda' is changed from a pointer to an actual value.
> > 
> >    Anyone want to take a stab at this? I'm not a big compiler
> > person myself... (Dave, you there?).
> 
>   Yes - I'm here :-)
> 
>   Typically - signal 11 problems from GNU's front-end are hardware 
>  memory issues....
> 
>   I will add that a quick test on a 3.3 system compiles this just
>  fine (Systems/C compiles it as well.)
> 
>   I would suspect hardware problems first.
> 
>   As I have learned from painful experience, *always* use ECC or at least
>  parity memory...
> 
> 	- Dave R. -

   Nawww... I've tried this on a bunch of different machines.. as a matter
of fact it replicates with gcc version 2.7.2.1 from December of last
year.  I find it hard to believe that I have 80 machines that all
exhibit the exact same memory failure... :-)

-John



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message