Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
91 lines (78 sloc) 3.61 KB
# This is a script to be run as part of The only time you'd
# want to run it by itself is if you're trying to cross-compile the
# system or if you're doing some kind of troubleshooting.
# This software is part of the SBCL system. See the README file for
# more information.
# This software is derived from the CMU CL system, which was
# written at Carnegie Mellon University and released into the
# public domain. The software is in the public domain and is
# provided with absolutely no warranty. See the COPYING and CREDITS
# files for more information.
echo //entering
# Do warm init stuff, e.g. building and loading CLOS, and stuff which
# can't be done until CLOS is running.
# Note that it's normal for the newborn system to think rather hard at
# the beginning of this process (e.g. using nearly 100Mb of virtual memory
# and >30 seconds of CPU time on a 450MHz CPU), and unless you built the
# system with the :SB-SHOW feature enabled, it does it rather silently,
# without trying to tell you about what it's doing. So unless it hangs
# for much longer than that, don't worry, it's likely to be normal.
echo //doing warm init
./src/runtime/sbcl \
--core output/cold-sbcl.core \
--sysinit /dev/null --userinit /dev/null <<-'EOF' || exit 1
;; Now that we use the compiler for macros, interpreted
;; /SHOW doesn't work until later in init.
#+sb-show (print "/hello, world!")
;; Until PRINT-OBJECT and other machinery is set up,
;; we want limits on printing to avoid infinite output.
;; (Don't forget to undo these tweaks after the printer
;; is set up. It'd be cleaner to use LET to make sure
;; that happens automatically, but LET is implemented
;; in terms of the compiler, and the compiler isn't
;; initialized yet.)
(setq *print-length* 10)
(setq *print-level* 5)
(setq *print-circle* t)
;; Do warm init.
#+sb-show (print "/about to LOAD warm.lisp")
(load "src/cold/warm.lisp")
;; Unintern no-longer-needed stuff before the possible PURIFY
#-sb-fluid (sb-impl::!unintern-init-only-stuff)
;; Now that the whole system is built, we don't need to
;; hobble the printer any more, so we can restore printer
;; control variables to their ANSI defaults.
(setq *print-length* nil)
(setq *print-level* nil)
(setq *print-circle* nil)
;; FIXME: Why is it that, at least on x86 sbcl-,
;; GC :FULL T isn't nearly as effective as PURIFY here?
;; (GC :FULL T gets us down to about 38 Mbytes, but PURIFY
;; gets us down to about 19 Mbytes.)
(sb-int:/show "done with warm.lisp, about to GC :FULL T")
(gc :full t)
;; resetting compilation policy to neutral values in
;; preparation for SAVE-LISP-AND-DIE as final SBCL core (not
;; in warm.lisp because SB-C::*POLICY* has file scope)
(sb-int:/show "setting compilation policy to neutral values")
(proclaim '(optimize (compilation-speed 1)
(debug 1)
(inhibit-warnings 1)
(safety 1)
(space 1)
(speed 1)))
(sb-int:/show "done with warm.lisp, about to SAVE-LISP-AND-DIE")
;; Even if /SHOW output was wanted during build, it's probably
;; not wanted by default after build is complete. (And if it's
;; wanted, it can easily be turned back on.)
#+sb-show (setf sb-int:*/show* nil)
;; The system is complete now, all standard functions are
;; defined.
(setq sb-c::*flame-on-necessarily-undefined-function* t)
(sb-ext:save-lisp-and-die "output/sbcl.core" :purify t)
Something went wrong with that request. Please try again.