OpenSolaris

The FPU status word in signal contexts after a floating point exception is zero,
but should reflect the current exceptions.
STEPS TO DUPLICATE
-------------------------
Compile the attached example:
cc -g -o tst-fpu tst-fpu.c
Run under CentOS 3.8 Brandz, and note that the SIGFPE handler
shows the status word exception bits are zero, and that the application
continues after returning from the exception.
EXPECTED VS ACTUAL RESULTS
-------------------------------------
Expected: Expect the status word to reflect the exceptions, and that the
application will only continue when the exception is explicitly masked in the
control word.
Actual: The status word exception bits are zero, and the application continues
ignoring the exception.
ERROR MESSAGES
---------------------
(No Answer)
SOURCE CODE
------------------
(No Answer)
SYSTEM INFORMATION
--------------------------
Hardware Platforms (AMD64-1, Non-Sun, ASUS K8V Delux, AMD Athlon., x64, 1GB, 100GB or more)
Operating Platforms (Sol1, Solaris 10 7/07, Solaris, JDS 3 Sun Java Desktop System Release 3, English)
SUBMITTER PROVIDED WORKAROUND
--------------------------
None.

Linux code needing to know the value of the status word at exception
time should examine ucp->uc_mcontext.fpregs->status rather than
ucp->uc_mcontext.fpregs->sw.

N/A