X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fearly-fasl.lisp;h=c592247c611daaf672b17ddef0a478ccde3ef269;hb=722703e7cbd3a4b279a4c1baab5d95df2c23cce9;hp=be0d3ab4370b81255ecc603e0b5c7df979721674;hpb=6cbe4d8ba6d7bc469d03a72514c789b1f3944878;p=sbcl.git diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index be0d3ab..c592247 100644 --- a/src/code/early-fasl.lisp +++ b/src/code/early-fasl.lisp @@ -36,57 +36,38 @@ ;;; the code for a character which terminates a fasl file header (defconstant +fasl-header-string-stop-char-code+ 255) -;;; 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+ 13) -;;; 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 -;;; when array headers or data element type uncertainty exist, and -;;; uses DATA-VECTOR-REF and DATA-VECTOR-SET only for VOPs. (Thus, -;;; full calls to DATA-VECTOR-REF and DATA-VECTOR-SET from older -;;; fasl files would fail, because there are no DEFUNs for these -;;; operations any more.) -;;; 5 = sbcl-0.6.8 has rearranged static symbols. -;;; 6 = sbcl-0.6.9, got rid of non-ANSI %DEFCONSTANT/%%DEFCONSTANT stuff -;;; and deleted a slot from DEBUG-SOURCE structure. -;;; 7 = around sbcl-0.6.9.8, merged SB-CONDITIONS package into SB-KERNEL -;;; 8 = sbcl-0.6.10.4 revived Gray stream support, changing stream layouts. -;;; 9 = deleted obsolete CONS-UNIQUE-TAG bytecode in sbcl-0.6.11.8 -;;; (somewhere in here also changes to AND and OR CTYPE layouts) -;;; 10 = new layout for CONDITION in sbcl-0.6.11.38 -;;; 11 = (a) new helper functions for MAKE-LOAD-FORM (HASH-TABLE) in -;;; sbcl-0.6.12.11 -;;; (b) new address space constants for OpenBSD in 0.6.12.17 -;;; (doesn't need separate version from (a) because the -;;; OpenBSD port was broken from sometime before 0.6.12.11 -;;; until the address space was changed) -;;; 12 = sbcl-0.6.12.22 added new SB-FASL package -;;; 13 = sbcl-0.6.12.x removed some elements from *STATIC-SYMBOLS* - -;;; the conventional file extension for fasl files on this -;;; architecture, e.g. "x86f" -(declaim (type (or simple-string null) *backend-fasl-file-type*)) -(defvar *backend-fasl-file-type* nil) - -;;; 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*) +;;; This value should be incremented when the system changes in such a +;;; way that it will no longer work reliably with old fasl files. In +;;; practice, I (WHN) fairly often neglect to increment it for CVS +;;; versions which break binary compatibility. But it certainly should +;;; be incremented for release versions which break binary +;;; compatibility. +(defconstant +fasl-file-version+ 27) +;;; (record of versions before 0.7.0 deleted in 0.7.1.41) +;;; 23 = sbcl-0.7.0.1 deleted no-longer-used EVAL-STACK stuff, +;;; causing changes in *STATIC-SYMBOLS*. +;;; 24 = sbcl-0.7.1.19 changed PCL service routines which might be +;;; called from macroexpanded code +;;; 25 = sbcl-0.7.1.41 (and immediately preceding versions, actually) +;;; introduced new functions to check for control stack exhaustion +;;; 26 = sbcl-0.7.2.4 or so added :VARIABLE :MACRO-EXPANSION to INFO codes +;;; 27 (2002-04-08) added MIGHT-CONTAIN-OTHER-TYPES? slot to CTYPE + +;;; the conventional file extension for our fasl files +(declaim (type simple-string *fasl-file-type*)) +(defvar *fasl-file-type* "fasl") -;;; information about below-Lisp-level linkage -;;; +;;;; information about below-Lisp-level linkage + ;;; Note: ;;; Assembler routines are named by full Lisp symbols: they ;;; have packages and that sort of native Lisp stuff associated ;;; with them. We can compare them with EQ. -;;; Foreign symbols are named by Lisp strings: the Lisp package +;;; Foreign symbols are named by Lisp STRINGs: the Lisp package ;;; system doesn't extend out to symbols in languages like C. ;;; We want to use EQUAL to compare them. ;;; *STATIC-FOREIGN-SYMBOLS* are static as opposed to "dynamic" (not -;;; as opposed to "extern"). The table contains symbols known at +;;; as opposed to C's "extern"). The table contains symbols known at ;;; the time that the program was built, but not symbols defined ;;; in object files which have been loaded dynamically since then. (declaim (type hash-table *assembler-routines* *static-foreign-symbols*)) @@ -95,14 +76,14 @@ ;;;; the FOP database -(declaim (simple-vector *fop-names* *fop-functions*)) +(declaim (simple-vector *fop-names* *fop-funs*)) ;;; a vector indexed by a FaslOP that yields the FOP's name (defvar *fop-names* (make-array 256 :initial-element nil)) ;;; a vector indexed by a FaslOP that yields a function of 0 arguments ;;; which will perform the operation -(defvar *fop-functions* +(defvar *fop-funs* (make-array 256 :initial-element (lambda () (error "corrupt fasl file: losing FOP")))) @@ -119,7 +100,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