0.6.12.29:

	cleanups pending from flaky2_branch and SB!FASL-package
		adventures, part II (more deleting)..
	..!COLD-INIT doesn't need to be a static symbol.
	..Does FDEFINITION-OBJECT need to be a static symbol? No.
	..Do we need the mysterious COLD-SETs of function
		values at the beginning of FINISH-SYMBOLS
		in genesis.lisp? No.
	..fasl version number change since !COLD-INIT is gone from
		*STATIC-SYMBOLS*

src/code/early-fasl.lisp

@@ -38,7 +38,7 @@
 
 ;;; 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)
+(defconstant +fasl-file-version+ 14)
 ;;; 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
@@ -62,7 +62,8 @@
 ;;;          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* 
+;;; 13 = sbcl-0.6.12.28 removed some elements from *STATIC-SYMBOLS* 
+;;; 14 = sbcl-0.6.12.29 removed more elements from *STATIC-SYMBOLS* 
 
 ;;; the conventional file extension for fasl files on this
 ;;; architecture, e.g. "x86f"

src/compiler/alpha/parms.lisp

@@ -173,7 +173,6 @@
     sb!kernel::internal-error
     sb!di::handle-breakpoint
     sb!di::handle-function-end-breakpoint
-    fdefinition-object
 
     ;; free Pointers
     *read-only-space-free-pointer*

src/compiler/generic/genesis.lisp

@@ -1137,18 +1137,16 @@
   ;; the function values for these things?? I.e. why do we need this
   ;; section at all? Is it because all the FDEFINITION stuff gets in
   ;; the way of reading function values and is too hairy to rely on at
-  ;; cold boot? FIXME: 5/6 of these are in *STATIC-SYMBOLS* in
+  ;; cold boot? FIXME: Most of these are in *STATIC-SYMBOLS* in
   ;; parms.lisp, but %HANDLE-FUNCTION-END-BREAKPOINT is not. Why?
   ;; Explain.
   (macrolet ((frob (symbol)
 	       `(cold-set ',symbol
 			  (cold-fdefinition-object (cold-intern ',symbol)))))
-    (frob !cold-init)
     (frob maybe-gc)
     (frob internal-error)
     (frob sb!di::handle-breakpoint)
-    (frob sb!di::handle-function-end-breakpoint)
-    (frob fdefinition-object))
+    (frob sb!di::handle-function-end-breakpoint))
 
   (cold-set '*current-catch-block*          (make-fixnum-descriptor 0))
   (cold-set '*current-unwind-protect-block* (make-fixnum-descriptor 0))

src/compiler/x86/parms.lisp

@@ -236,7 +236,6 @@
     sb!impl::*!initial-fdefn-objects*
 
     ;; functions that the C code needs to call
-    sb!impl::!cold-init
     maybe-gc
     sb!kernel::internal-error
     sb!di::handle-breakpoint

version.lisp-expr

@@ -15,4 +15,4 @@
 ;;; versions, and a string like "0.6.5.12" is used for versions which
 ;;; aren't released but correspond only to CVS tags or snapshots.
 
-"0.6.12.28"
+"0.6.12.29"