Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Apr 1996 00:29:21 -0400 (EDT)
From:      "Marc G. Fournier" <scrappy@ki.net>
To:        David Greenman <davidg@Root.COM>
Cc:        current@freebsd.org
Subject:   Re: Can someone explain why... 
Message-ID:  <Pine.BSI.3.92.960414002413.200A-100000@freebsd.ki.net>
In-Reply-To: <199604140418.VAA03036@Root.COM>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 13 Apr 1996, David Greenman wrote:

> >...I get these occasionally while attempting to compile a kernel:
> >
> >freebsd# make
> >cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit  -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes  -Winline -g -nostdinc -I. -I../.. -I../../sys -I../../../include -DI486_CPU -DCOMPAT_43 -DDEVFS -DNFS -DFFS -DINET -DDODUMP -DK
ERN
> >EL  ../../kern/subr_xxx.c
> >cc: Internal compiler error: program cc1 got fatal signal 10
> >*** Error code 1
>
>    Seemingly random signal 10 and 11s almost always indicates a hardware
> problem. It's usually a problem with memory or the secondary cache, but has
> also been known to be caused by flakey disk controllers, motherboards, and
> CPUs. I don't think this is disk controller related because you are also
> having weird kernel panics in areas where I know no bugs exist. Several years
> ago we had some VM system problems which would sometimes cause similar
> behavior, but the causes of these problems are well understood and have been
> fixed for years.
>    The only way to troubleshoot this kind of problem is to first look at your
> motherboard settings for correctness and then start replacing components until
> the problem goes away. I would try changing the memory first.
>
	Okay, I could probably accept this (and most likely will in the end),
but why would disabling -O allow it to compile, and then if I remove the
object file, re-enable -O cause it to fail exactly the same way?

	Basically, if I tried to compile it without -O, everything ran as
expected, whereas if I tried to use -O, it failed at exactly the same point
each time (as if it was tripping over a piece of code that it just couldn't
optimize).  The funny thing was, if I popped it up to -O2, it also allowed
it to compile as expected.


Marc G. Fournier                                  scrappy@ki.net
Systems Administrator @ ki.net               scrappy@freebsd.org




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.92.960414002413.200A-100000>