On 4-Jun-08, at 8:40 AM, Nikodemus Siivola wrote:
> Update of /cvsroot/sbcl/sbcl
> In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv19220
> Modified Files:
> NEWS OPTIMIZATIONS build-order.lisp-expr
> package-data-list.lisp-expr version.lisp-expr
> Log Message:
> 22.214.171.124: refactor handling of constants in the compiler
> * Coalesce non-circular lists, bit-vectors, and non-base-strings in
> file-compiler. (We could do more, but these are the "easy" ones.)
> care of OPTIMIZATIONS #34 in practice: outside the file compiler
> one can
> still trick the system into similar behaviour, but that seems a
> academic concern.
> * Never go through SYMBOL-VALUE at runtime to fetch the value of a
> variable in compiled code.
> * Gets rid of INFO :VARIABLE :CONSTANT-VALUE, and just uses SYMBOL-
> VALUE to
> store constant values.
(trimmed unlikely to be relevant changes)
126.96.36.199 is confused between the host's and the cross-compiler's
definition of, e.g., most-positive-fixnum. This causes a failure in
from-xc/target-sxhash when building a 32 bit SBCL from a 64 bit host.
(eval-when (:compile-toplevel :load-toplevel)
(format t "m-p-f: ~A~%" most-positive-fixnum))
to target-sxhash.lisp confirms that "; compiling (FORMAT T ...)m-p-f:
I'm not certain how to tackle this one.