0.8.21.8:

	Building a 64-bit target with a 32-bit host works again.
        * most-positive-fixnum -> sb!xc:most-positive-fixnum in
          !DEFINE-BYTE-BASHERS

diff --git a/src/code/bit-bash.lisp b/src/code/bit-bash.lisp
index 9a6853d..a0c8319 100644 (file)
--- a/src/code/bit-bash.lisp
+++ b/src/code/bit-bash.lisp
@@ -132,7 +132,7 @@
   (let* ((bytes-per-word (/ n-word-bits bitsize))
          (byte-offset `(integer 0 (,bytes-per-word)))
          (byte-count `(integer 1 (,bytes-per-word)))
-         (max-bytes (ash most-positive-fixnum
+         (max-bytes (ash sb!xc:most-positive-fixnum
                          ;; FIXME: this reflects code contained in the
                          ;; original bit-bash.lisp, but seems very
                          ;; nonsensical.  Why shouldn't we be able to

diff --git a/version.lisp-expr b/version.lisp-expr
index c7ce455..4233c43 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.21.7"
+"0.8.21.8"