>> 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 majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
