1 ;;;; "warm initialization": initialization which comes after cold init
3 ;;;; This software is part of the SBCL system. See the README file for
6 ;;;; This software is derived from the CMU CL system, which was
7 ;;;; written at Carnegie Mellon University and released into the
8 ;;;; public domain. The software is in the public domain and is
9 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
10 ;;;; files for more information.
12 (in-package "COMMON-LISP-USER")
14 ;;;; general warm init compilation policy
16 (proclaim '(optimize (compilation-speed 1)
17 (debug #+sb-show 2 #-sb-show 1)
26 ;;; Our cross-compilation host is out of the picture now, so we no
27 ;;; longer need to worry about collisions between our package names
28 ;;; and cross-compilation host package names, so now is a good time to
29 ;;; rename any package with a bootstrap-only name SB!FOO to its
30 ;;; permanent name SB-FOO.
32 ;;; (In principle it might be tidier to do this when dumping the cold
33 ;;; image in genesis, but in practice the logic might be a little
34 ;;; messier because genesis dumps both symbols and packages, and we'd
35 ;;; need to make sure that dumped symbols were renamed in the same way
36 ;;; as dumped packages. Or we could do it in cold init, but it's
37 ;;; easier to experiment with and debug things here in warm init than
38 ;;; in cold init, so we do it here instead.)
39 (let ((boot-prefix "SB!")
41 (dolist (package (list-all-packages))
42 (let ((old-package-name (package-name package)))
43 (when (and (>= (length old-package-name) (length boot-prefix))
44 (string= boot-prefix old-package-name
45 :end2 (length boot-prefix)))
46 (let ((new-package-name (concatenate 'string
48 (subseq old-package-name
49 (length boot-prefix)))))
50 (rename-package package
52 (package-nicknames package)))))))
54 ;;; FIXME: This nickname is a deprecated hack for backwards
55 ;;; compatibility with code which assumed the CMU-CL-style
56 ;;; SB-ALIEN/SB-C-CALL split. That split went away and was deprecated
57 ;;; in 0.7.0, so we should get rid of this nickname after a while.
58 (let ((package (find-package "SB-ALIEN")))
59 (rename-package package
60 (package-name package)
61 (cons "SB-C-CALL" (package-nicknames package))))
63 (let ((package (find-package "SB-SEQUENCE")))
64 (rename-package package (package-name package) (list "SEQUENCE")))
66 ;;;; compiling and loading more of the system
68 ;;; FIXME: CMU CL's pclcom.lisp had extra optional stuff wrapped around
69 ;;; COMPILE-PCL, at least some of which we should probably have too:
71 ;;; (with-compilation-unit
72 ;;; (:optimize '(optimize (debug #+(and (not high-security) small) .5
73 ;;; #-(or high-security small) 2
74 ;;; #+high-security 3)
75 ;;; (speed 2) (safety #+(and (not high-security) small) 0
76 ;;; #-(or high-security small) 2
77 ;;; #+high-security 3)
78 ;;; (inhibit-warnings 2))
79 ;;; :optimize-interface '(optimize-interface #+(and (not high-security) small)
81 ;;; #+high-security (safety 3))
82 ;;; :context-declarations
83 ;;; '((:external (declare (optimize-interface (safety #-high-security 2 #+high-
85 ;;; (debug #-high-security 1 #+high-s
87 ;;; ((:or :macro (:match "$EARLY-") (:match "$BOOT-"))
88 ;;; (declare (optimize (speed 0))))))
90 ;;; FIXME: This has mutated into a hack which crudely duplicates
91 ;;; functionality from the existing mechanism to load files from
92 ;;; build-order.lisp-expr, without being quite parallel. (E.g. object
93 ;;; files end up alongside the source files instead of ending up in
94 ;;; parallel directory trees.) Maybe we could merge the filenames here
95 ;;; into build-order.lisp-expr with some new flag (perhaps :WARM) to
96 ;;; indicate that the files should be handled not in cold load but
98 (dolist (stem '(;; CLOS, derived from the PCL reference implementation
100 ;; This PCL build order is based on a particular
101 ;; (arbitrary) linearization of the declared build
102 ;; order dependencies from the old PCL defsys.lisp
103 ;; dependency database.
104 #+nil "src/pcl/walk" ; #+NIL = moved to build-order.lisp-expr
107 "SRC;PCL;COMPILER-SUPPORT"
124 "SRC;PCL;GENERIC-FUNCTIONS"
135 "SRC;PCL;DOCUMENTATION"
136 "SRC;PCL;PRINT-OBJECT"
140 ;; miscellaneous functionality which depends on CLOS
141 "SRC;CODE;FORCE-DELAYED-DEFBANGMETHODS"
142 "SRC;CODE;LATE-CONDITION"
144 ;; CLOS-level support for the Gray OO streams
145 ;; extension (which is also supported by various
146 ;; lower-level hooks elsewhere in the code)
147 "SRC;PCL;GRAY-STREAMS-CLASS"
148 "SRC;PCL;GRAY-STREAMS"
150 ;; CLOS-level support for User-extensible sequences.
153 ;; other functionality not needed for cold init, moved
154 ;; to warm init to reduce peak memory requirement in
157 "SRC;CODE;DESCRIBE-POLICY"
163 #+win32 "SRC;CODE;WARM-MSWIN"
164 "SRC;CODE;RUN-PROGRAM"))
166 (let ((fullname (concatenate 'string "SYS:" stem ".LISP")))
167 (sb-int:/show "about to compile" fullname)
168 (flet ((report-recompile-restart (stream)
169 (format stream "Recompile file ~S" fullname))
170 (report-continue-restart (stream)
172 "Continue, using possibly bogus file ~S"
173 (compile-file-pathname fullname))))
176 (multiple-value-bind (output-truename warnings-p failure-p)
177 (if *compile-files-p*
178 (compile-file fullname)
179 (compile-file-pathname fullname))
180 (declare (ignore warnings-p))
181 (sb-int:/show "done compiling" fullname)
182 (cond ((not output-truename)
183 (error "COMPILE-FILE of ~S failed." fullname))
187 (error "FAILURE-P was set when creating ~S."
190 :report report-recompile-restart
191 (go retry-compile-file))
193 :report report-continue-restart
194 (setf failure-p nil)))
195 ;; Don't leave failed object files lying around.
196 (when (and failure-p (probe-file output-truename))
197 (delete-file output-truename)
198 (format t "~&deleted ~S~%" output-truename))))
199 ;; Otherwise: success, just fall through.
201 (unless (load output-truename)
202 (error "LOAD of ~S failed." output-truename))
203 (sb-int:/show "done loading" output-truename))))))
205 ;;;; setting package documentation
207 ;;; While we were running on the cross-compilation host, we tried to
208 ;;; be portable and not overwrite the doc strings for the standard
209 ;;; packages. But now the cross-compilation host is only a receding
210 ;;; memory, and we can have our way with the doc strings.
211 (sb-int:/show "setting package documentation")
212 #+sb-doc (setf (documentation (find-package "COMMON-LISP") t)
213 "public: home of symbols defined by the ANSI language specification")
214 #+sb-doc (setf (documentation (find-package "COMMON-LISP-USER") t)
215 "public: the default package for user code and data")
216 #+sb-doc (setf (documentation (find-package "KEYWORD") t)
217 "public: home of keywords")