Date: Tue, 25 Nov 1997 08:16:09 -0700 From: Nate Williams <nate@mt.sri.com> To: Mike Smith <mike@smith.net.au> Cc: Nate Williams <nate@mt.sri.com>, shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG Subject: Re: Compiler Bug??? Message-ID: <199711251516.IAA27098@mt.sri.com> In-Reply-To: <199711250655.RAA00340@word.smith.net.au> References: <199711250603.XAA25821@mt.sri.com> <199711250655.RAA00340@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711251516.IAA27098>