Date: Tue, 25 Nov 1997 17:40:49 -0800 (PST) From: Simon Shapiro <shimon@simon-shapiro.org> To: Nate Williams <nate@mt.sri.com> Cc: freebsd-current@FreeBSD.ORG, Mike Smith <mike@smith.net.au> Subject: Re: Compiler Bug??? Message-ID: <XFMail.971125174049.shimon@Simon-Shapiro.ORG> In-Reply-To: <199711251516.IAA27098@mt.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25-Nov-97 Nate Williams wrote: >> > Guess what, you have bad memory! Seriously, this is not a >> > compiler bug, >> > but something in your hardware that is hosed up. Either the >> > memory is >> > bad, the timings are bad, the cache is bad, or some combination of >> > the >> > above is bad. Compiler bugs don't go away on reboots, but >> > corrupted >> > memory does. >> >> ... just to clarify here, as I am reading Simon slightly differently >> from you; >> >> - code built while running UP works. >> - code built while running SMP fails. > > Actually, code built while running SMP was failing, but causing a > boot > into UP caused it to work, and then going back to SMP caused it to > still > work. > >> I'm inclined to agree with Nate in that it's unlikely that you have >> found a compiler bug, more likely an environment (eg. kernel) bug >> that >> is causing you some serious grief. Seems that way. The sequence as not critical. Just putting moderate load on the SMP kernel would cause the system to go googoo. ONE of the symptoms was bad compiles. Another was a crashing gcc, etc. Simon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.971125174049.shimon>