0.8.1.52:

	Comment out the meat in ppc/linux os_restore_fp_control, because
	although that superficially worsens our floating point handling
	on that platform,
	...RUN-PROGRAM no longer segfaults with such enthusiasm;
	...our floating point handling was quite poor in any case, as
		evidenced by (/ 1.0 0.0).

diff --git a/src/runtime/ppc-linux-os.c b/src/runtime/ppc-linux-os.c
index 443c733..9b806d3 100644 (file)
--- a/src/runtime/ppc-linux-os.c
+++ b/src/runtime/ppc-linux-os.c
@@ -110,7 +110,13 @@ os_restore_fp_control(os_context_t *context)
        just guessing. The 255, on the other hand, is a valid constant
        -- it says "move everything in the upper word into the floating
        point control register. -- CSR, 2002-07-16 */
+
+    /* FIXME: it appears that the above text is quite accurate, in the
+       sense that this
+
     asm ("stw %0, 12(31); lfd 0, 8(31); mtfsf 255, 0" : : "r" (control) : "r31");
+
+    no longer works. */
 }
 
 void 

diff --git a/version.lisp-expr b/version.lisp-expr
index a6eec2a..b9acd70 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; 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.1.51"
+"0.8.1.52"