From owner-freebsd-current  Sat May 29  5:43:36 1999
Delivered-To: freebsd-current@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id 6B10B1522E
	for <current@FreeBSD.ORG>; Sat, 29 May 1999 05:43:32 -0700 (PDT)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA30183;
	Sat, 29 May 1999 22:43:22 +1000
Date: Sat, 29 May 1999 22:43:22 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199905291243.WAA30183@godzilla.zeta.org.au>
To: cracauer@cons.org, jkh@zippy.cdrom.com
Subject: Re: FP exceptions broken (Re: Interesting bogons from last night's 4.0 snapshot.)
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> JFYI - don't want us getting *too* complacent with -current now, do we? :-)
>
>Floating point exceptions are also broken, they always behave like
>masked, even if you unmask some explicitly with fpsetmask().
>
>Even worse, a wrong result is returned if an exception had to be
>thrown, while the result is right for masked exceptions.

This seems to have fixed itself:

May 23 kernel: fails
May 24 kernel: works
May 28 kernel: works

For the failing case, the FPU seems to be working properly but no CPU
exception 16 is received for the unmasked FPU exception, and CR0_TS is
in an unusualy state (not set) at the end of another test program.

Bruce


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