X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fearly-fasl.lisp;h=a0f5c64879bd078684ce1febe9f07f7ed1798a05;hb=8eb6f7d3da3960c827b704e23b5a47008274be7d;hp=9bd0c45544d2f78b43d5f75adf80a527f20450e1;hpb=d3df7e8508d37a831ecf06a2c42ddb6ede1d99fa;p=sbcl.git diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index 9bd0c45..a0f5c64 100644 --- a/src/code/early-fasl.lisp +++ b/src/code/early-fasl.lisp @@ -38,7 +38,7 @@ ;;; This value should be incremented when the system changes in such ;;; a way that it will no longer work reliably with old fasl files. -(defconstant +fasl-file-version+ 18) +(defconstant +fasl-file-version+ 21) ;;; 2 = sbcl-0.6.4 uses COMPILE-OR-LOAD-DEFGENERIC. ;;; 3 = sbcl-0.6.6 uses private symbol, not :EMPTY, for empty HASH-TABLE slot. ;;; 4 = sbcl-0.6.7 uses HAIRY-DATA-VECTOR-REF and HAIRY-DATA-VECTOR-SET @@ -73,19 +73,23 @@ ;;; meaning of FOP-FSET, and changed the layouts of various ;;; internal compiler structures (e.g. DEFSTRUCT CLAMBDA) ;;; 18 = sbcl-0.pre7.39 swapped FUNCTION-POINTER-TYPE and -;;; INSTANCE-POINTER-TYPE low-level type codes to help with +;;; INSTANCE-POINTER-LOWTAG low-level type codes to help with ;;; the PPC port +;;; (In 0.pre7.48, the low-level object layout of SYMBOL on the +;;; non-X86 ports changed. I forgot to bump the fasl version number: +;;; I only have an X86.. -- WHN) +;;; 19 = sbcl-0.pre7.50 deleted byte-compiler-related low-level type codes +;;; 20 = sbcl-0.pre7.51 modified names and layouts of +;;; physical-environment-related structures in the compiler +;;; 21 = sbcl-0.pre7.62 finally incremented the version after several +;;; incompatible changes in earlier versions: many many symbols +;;; renamed, changes in globaldb representation of constants +;;; and inline functions, and change in the value of +;;; INTERNAL-TIME-UNITS-PER-SECOND ;;; the conventional file extension for our fasl files (declaim (type simple-string *fasl-file-type*)) (defvar *fasl-file-type* "fasl") - -;;; This is a sort of pun that we inherited from CMU CL. For ordinary, -;;; non-byte-coded fasl files, the "implementation" is basically the -;;; CPU. For byte-coded fasl files, the "implementation" is whether -;;; the data are stored big-endianly or little-endianly. -(defun backend-byte-fasl-file-implementation () - *backend-byte-order*) ;;; information about below-Lisp-level linkage ;;; @@ -130,7 +134,7 @@ ;;; the FASL file we're reading from (defvar *fasl-input-stream*) -(declaim (type lisp-stream *fasl-input-stream*)) +(declaim (type ansi-stream *fasl-input-stream*)) (defvar *load-print* nil #!+sb-doc