--core output/cold-sbcl.core \
--sysinit /dev/null --userinit /dev/null <<-'EOF' || exit 1
- (sb!int:/show "hello, world!")
+ ;; 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.
- (let ((*print-length* 5)
- (*print-level* 5))
- (sb!int:/show "about to LOAD warm.lisp")
- (load "src/cold/warm.lisp"))
+ #+sb-show (print "/about to LOAD warm.lisp")
+ (load "src/cold/warm.lisp")
;; Unintern no-longer-needed stuff before the possible PURIFY
;; in SAVE-LISP-AND-DIE.
#-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-0.6.12.46,
+ ;; 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.)
+ (let ((*gc-notify-stream* *standard-output*))
+ (sb-int:/show "done with warm.lisp, about to GC :FULL T")
+ (gc :full t))
+
(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
projects / sbcl.git / blobdiff