X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fearly-fasl.lisp;h=15cf2d0ed34465246251ba3d5ac750646b81d6f5;hb=d48e55084636a84d1b54f1f7370fa98c55f3ec6e;hp=6defa1c625afefc2671dd3301564515f3f6ea88d;hpb=aca45f35fc54bc29e2c79397e3538ff27f6e0db9;p=sbcl.git diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index 6defa1c..15cf2d0 100644 --- a/src/code/early-fasl.lisp +++ b/src/code/early-fasl.lisp @@ -33,23 +33,80 @@ ;;; against. (defparameter *fasl-header-string-start-string* "# FASL") +(macrolet ((define-fasl-format-features () + (let (;; master value for *F-P-A-F-F* + (fpaff '(:sb-thread))) + `(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 -(defconstant +fasl-header-string-stop-char-code+ 255) +(def!constant +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. In -;;; practice, I (WHN) fairly often neglect to increment it for CVS +;;; practice, I (WHN) have often forgotten 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+ 25) -;;; (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 +(def!constant +fasl-file-version+ 49) +;;; (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. ;;; the conventional file extension for our fasl files (declaim (type simple-string *fasl-file-type*))