From owner-freebsd-hackers Sat Nov 8 19:40:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10480 for hackers-outgoing; Sat, 8 Nov 1997 19:40:21 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10473 for ; Sat, 8 Nov 1997 19:40:18 -0800 (PST) (envelope-from digital@www2.shoppersnet.com) Received: (from digital@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id TAA15374; Sat, 8 Nov 1997 19:42:51 -0800 (PST) Date: Sat, 8 Nov 1997 19:42:51 -0800 (PST) From: Howard Lew To: Tony Kimball cc: hackers@FreeBSD.ORG Subject: Re: Newest Pentium bug (fatal) In-Reply-To: <199711082030.OAA17326@pobox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 8 Nov 1997, Tony Kimball wrote: > ! Compared with the aforementioned > ! floating-point bug, this seems like a much bigger deal. > > No, the FP bug was infinitely worse, because it would silently give > wrong answers. You could crash the Thai Bhat by accident with an old > Pentium chip. In this case, the machine is locked -- no one is going > to misinterpret that. Indeed, a non-broken compiler would never emit > the code. This is no worse than running Windows on a computer without > the bug, right? In both cases, pathological code can lock the > machine. And millions run Windows voluntarily -- or at least don't > try hard enough to not run Windows in order to overcome the coercivity > of the environment. > For Windows users this bug should not be much of a problem unless viruses start popping up taking advantage of the bug. For FreeBSD it is not very comforting to know that any misbehaving user can lock up your shell machine, but in a controlled environment this should not be a problem.