(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))))))))
+ (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)
;;; versions which break binary compatibility. But it certainly should
;;; be incremented for release versions which break binary
;;; compatibility.
-(def!constant +fasl-file-version+ 45)
-;;; (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
-;;; <dan`b> what happened this month to stalate the fasls?
-;;; <Krystof_> I think I renumbered everything again
-;;; <Krystof_> simple-array-unsigned-byte-7, probably
-;;; <Krystof_> (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.
+(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*))
;;; 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))
+
\f
;;;; the FOP database
;;; which will perform the operation
(defvar *fop-funs*
(make-array 256
- :initial-element (lambda ()
- (error "corrupt fasl file: losing FOP"))))
-\f
-;;;; other miscellaneous loading-related stuff
-
+ :initial-element (lambda ()
+ (error "corrupt fasl file: losing FOP"))))
\f
;;;; variables
(defvar *fasl-input-stream*)
(declaim (type ansi-stream *fasl-input-stream*))
-(defvar *load-print* nil
- #!+sb-doc
- "the default for the :PRINT argument to LOAD")
-(defvar *load-verbose* nil
- ;; Note that CMU CL's default for this was T, and ANSI says it's
- ;; implementation-dependent. We choose NIL on the theory that it's
- ;; a nicer default behavior for Unix programs.
- #!+sb-doc
- "the default for the :VERBOSE argument to LOAD")
-
(defvar *load-code-verbose* nil)
-
projects / sbcl.git / blobdiff