X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fearly-fasl.lisp;h=6c60a2af2c3cc07607c6a3562776d3326363bf76;hb=82cd148d729c241e79c8df04b700beec1b7c55de;hp=a051605e25cb46910decbbf9ceaa1ef5dc1a7e2d;hpb=c75cf4e142aaf9a72433ea6db778d8111a0b1c83;p=sbcl.git diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index a051605..6c60a2a 100644 --- a/src/code/early-fasl.lisp +++ b/src/code/early-fasl.lisp @@ -35,7 +35,7 @@ (macrolet ((define-fasl-format-features () (let (;; master value for *F-P-A-F-F* - (fpaff '(:sb-thread :sb-package-locks :sb-unicode :gencgc))) + (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 @@ -76,7 +76,7 @@ ;;; versions which break binary compatibility. But it certainly should ;;; be incremented for release versions which break binary ;;; compatibility. -(def!constant +fasl-file-version+ 75) +(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). @@ -105,6 +105,15 @@ ;;; 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*))