void
os_restore_fp_control(os_context_t *context)
{
- /* FIXME (in two parts):
- Firstly, what happens in alpha linux inside the signal handler?
- Does the floating point control state get cleared as in other
- Linuxes?
-
- Secondly, how do we put it back if so? It will probably involve
- something to do with
-
- context->uc_mcontext.sc_fpcr
-
- (maybe a simple assembly statement will be enough)
- */
+ /* FIXME: 0x7E0000 is defined as something useful in constants.h,
+ but without the L, which would probably lead to 32/64-bit
+ errors if we simply used it here. Ugh. CSR, 2003-09-15 */
+ arch_set_fp_control(os_context_fp_control(context) & ~(0x7e0000L));
}
void os_flush_icache(os_vm_address_t address, os_vm_size_t length)
(* (logandc1 (max -29303 b) 4) b)
(abs (logorc1 (+ (logandc1 -11 b) 2607688420) -31153924)))
(logeqv (max a 0) b))))
+
+;;; Alpha floating point modes weren't being reset after an exception,
+;;; leading to an exception on the second compile, below.
+(compile nil '(lambda (x y) (declare (type (double-float 0.0d0) x y)) (/ x y)))
+(handler-bind ((division-by-zero #'abort))
+ (/ 1.0 0.0))
+(compile nil '(lambda (x y) (declare (type (double-float 0.0d0) x y)) (/ x y)))
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"0.8.3.66"
+"0.8.3.67"