X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fearly-fasl.lisp;h=6c60a2af2c3cc07607c6a3562776d3326363bf76;hb=4ba392170e98744f0ef0b8e08a5d42b988f1d0c9;hp=029d24a751d053b0e5b3e83f37450c79f908c28d;hpb=4a59cac8038dde1232b82fed1470b184b68cf6e1;p=sbcl.git diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index 029d24a..6c60a2a 100644 --- a/src/code/early-fasl.lisp +++ b/src/code/early-fasl.lisp @@ -35,38 +35,38 @@ (macrolet ((define-fasl-format-features () (let (;; master value for *F-P-A-F-F* - (fpaff '(:sb-thread :sb-package-locks))) - `(progn - ;; a list of *(SHEBANG-)FEATURES* flags which affect - ;; binary compatibility, i.e. which must be the same - ;; between the SBCL which compiles the code and the - ;; SBCL which executes the code - ;; - ;; This is a property of SBCL executables in the - ;; abstract, not of this particular SBCL executable, - ;; so any flag in this list may or may not be present - ;; in the *FEATURES* list of this particular build. - (defparameter *features-potentially-affecting-fasl-format* - ',fpaff) - ;; a string representing flags of *F-P-A-F-F* which - ;; are in this particular build - ;; - ;; (A list is the natural logical representation for - ;; this, but we represent it as a string because - ;; that's physically convenient for writing to and - ;; reading from fasl files, and because we don't - ;; need to do anything sophisticated with its - ;; logical structure, just test it for equality.) - (defparameter *features-affecting-fasl-format* - ,(let ((*print-pretty* nil)) - (prin1-to-string - (sort - (copy-seq - (intersection sb-cold:*shebang-features* fpaff)) - #'string< - :key #'symbol-name)))))))) + (fpaff '(:sb-thread :sb-package-locks :sb-unicode :gencgc :ud2-breakpoints))) + `(progn + ;; a list of *(SHEBANG-)FEATURES* flags which affect + ;; binary compatibility, i.e. which must be the same + ;; between the SBCL which compiles the code and the + ;; SBCL which executes the code + ;; + ;; This is a property of SBCL executables in the + ;; abstract, not of this particular SBCL executable, + ;; so any flag in this list may or may not be present + ;; in the *FEATURES* list of this particular build. + (defparameter *features-potentially-affecting-fasl-format* + ',fpaff) + ;; a string representing flags of *F-P-A-F-F* which + ;; are in this particular build + ;; + ;; (A list is the natural logical representation for + ;; this, but we represent it as a string because + ;; that's physically convenient for writing to and + ;; reading from fasl files, and because we don't + ;; need to do anything sophisticated with its + ;; logical structure, just test it for equality.) + (defparameter *features-affecting-fasl-format* + ,(let ((*print-pretty* nil)) + (prin1-to-string + (sort + (copy-seq + (intersection sb-cold:*shebang-features* fpaff)) + #'string< + :key #'symbol-name)))))))) (define-fasl-format-features)) - + ;;; the code for a character which terminates a fasl file header (def!constant +fasl-header-string-stop-char-code+ 255) @@ -76,40 +76,44 @@ ;;; versions which break binary compatibility. But it certainly should ;;; be incremented for release versions which break binary ;;; compatibility. -(def!constant +fasl-file-version+ 51) -;;; (record of versions before 2003 deleted in 2003-04-26/0.pre8.107 or so) -;;; 38: (2003-01-05) changed names of internal SORT machinery -;;; 39: (2003-02-20) in 0.7.12.1 a slot was added to -;;; DEFSTRUCT-SLOT-DESCRIPTION -;;; 40: (2003-03-11) changed value of (SXHASH NIL) -;;; 41: (2003-04-26) enforced binary incompatibility between +SB-THREAD -;;; and -SB-THREAD builds -;;; 42: (2003-05-22) %NAME slot changed to NAME in -;;; DEFSTRUCT-SLOT-DESCRIPTION -;;; 43: (2003-07-18) Something could easily have changed incompatibly in -;;; recent maintenance, e.g. from (VECTOR NIL)-as-string support. -;;; (And experimental results suggest that compatibility was broken -;;; between about 0.8.1.29 and 0.8.1.39.) -;;; 44: (2003-08-25) various changes leading up to 0.8.3 -;;; what happened this month to stalate the fasls? -;;; I think I renumbered everything again -;;; simple-array-unsigned-byte-7, probably -;;; (thanks to pfdietz) -;;; 45: (2003-10-02) I (WHN) incremented the version for the 0.8.4 -;;; release because I couldn't immediately convince myself that -;;; .fasl files could never possibly ever refer to the SB-C -;;; CONTINUATION-related data types which were changed -;;; incompatibly in 0.8.3.62. -;;; 46: (2003-11-11) Tim Daly, Jr. (and Christophe Rhodes) reported -;;; .fasl incompatibility on sbcl-devel 2003-11-09. -;;; 47: (2003-11-30) Static variables were rearranged in 0.8.6.11. -;;; 48: (2004-03-01) Renumbered all the widetags to allow for more -;;; microefficiency in sbcl-0.8.8.10 -;;; 49: (2004-05-04) Changed implementation of DEFFOO macros and the -;;; functions they expand to. -;;; 50: (2004-05-20) Changed %COMPILER-DEFUN signature again. -;;; 51: (2004-07-24) Package locks (SBCL 0.8.12.7) changed signature of -;;; %DEFPACKAGE. +(def!constant +fasl-file-version+ 78) +;;; (description of versions before 0.9.0.1 deleted in 0.9.17) +;;; 56: (2005-05-22) Something between 0.9.0.1 and 0.9.0.14. My money is +;;; on 0.9.0.6 (MORE CASE CONSISTENCY). +;;; 57: (2005-06-12) Raw slot rearrangement in 0.9.1.38 +;;; 58: (2005-08-16) Multiple incompatible changes between 0.9.3 and 0.9.3.60 +;;; 59: (2005-09-18) METAOBJECT implementation, removal of INSTANCE and +;;; FUNCALLABLE-INSTANCE classes. +;;; 60: (2005-10-24) Bumped for 0.9.6 +;;; 61: (2005-11-06) Improved source location recording added extra parameters +;;; to multiple %DEFMUMBLE functions. +;;; 62: (2005-12-30) Make the count of FASL header counted strings +;;; a 32-bit value also on 64-bit platforms. +;;; 63: (2006-01-27) Shuffle storage classes around to reduce the error +;;; trap information size on RISCy platforms. +;;; 64: (2006-03-24) New calling convention for unknown-values on x86 and +;;; x86-64. Also (belatedly) PPC/gencgc, including :gencgc on FPAFF. +;;; 65: (2006-04-11) Package locking interface changed. +;;; 66: (2006-05-13) Fopcompiler +;;; 67: (2006-07-25) Reports on #lisp about 0.9.13 fasls being invalid on +;;; 0.9.14.something +;;; 68: (2006-08-14) changed number of arguments of LOAD-DEFMETHOD +;;; 69: (2006-08-17) changed validity of various initargs for methods +;;; 70: (2006-09-13) changes to *PSEUDO-ATOMIC* on x86 and x86-64 +;;; 71: (2006-11-19) CLOS calling convention changes +;;; 72: (2006-12-05) Added slot to the primitive function type +;;; 73: (2007-04-13) Changed a hash function +;;; 74: (2007-06-05) UNWIND-TO-FRAME-AND-CALL +;;; 75: (2007-08-06) FD-STREAM layout changes +;;; 76: (2007-10-05) MUTEX layout changes +;;; 77: (2007-11-08) Essentially obsolete fasl-file-version, fasls are now +;;; considered compatible only when the version numbers of the compiling +;;; SBCL instance is exactly the same as the one of the loading instance. +;;; Further fasl-file-version bumps should only be done for real changes +;;; in the fasl format, not for changes in function/macro signatures or +;;; lisp data structures. +;;; 78: (2010-04-02) Add FOP-{SMALL-,}NAMED-PACKAGE, remove FOP-NORMAL-LOAD +;;; and FOP-MAYBE-COLD-LOAD. ;;; the conventional file extension for our fasl files (declaim (type simple-string *fasl-file-type*)) @@ -121,16 +125,9 @@ ;;; 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 -;;; 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 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*)) +(declaim (type hash-table *assembler-routines*)) (defvar *assembler-routines* (make-hash-table :test 'eq)) -(defvar *static-foreign-symbols* (make-hash-table :test 'equal)) + ;;;; the FOP database @@ -143,8 +140,8 @@ ;;; which will perform the operation (defvar *fop-funs* (make-array 256 - :initial-element (lambda () - (error "corrupt fasl file: losing FOP")))) + :initial-element (lambda () + (error "corrupt fasl file: losing FOP")))) ;;;; variables