X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;ds=sidebyside;f=make-target-2.sh;h=fb85d1de08edf35858475f1940b7b0431743d59a;hb=4a0ab5193096ca70dbbf43bb21418544f6d018b7;hp=3d7990fb079c0bd1124b1c859bdce6bfcb914a3c;hpb=a530bbe337109d898d5b4a001fc8f1afa3b5dc39;p=sbcl.git

diff --git a/make-target-2.sh b/make-target-2.sh
index 3d7990f..fb85d1d 100644
--- a/make-target-2.sh
+++ b/make-target-2.sh
@@ -13,7 +13,7 @@
 # provided with absolutely no warranty. See the COPYING and CREDITS
 # files for more information.
 
-echo //entering make-host-2.sh
+echo //entering make-target-2.sh
 
 # Do warm init stuff, e.g. building and loading CLOS, and stuff which
 # can't be done until CLOS is running.
@@ -28,12 +28,30 @@ echo //doing warm init
 ./src/runtime/sbcl \
 --core output/cold-sbcl.core \
 --sysinit /dev/null --userinit /dev/null <<-'EOF' || exit 1
-        (sb!int:/show "hello, world!")
-	(let ((*print-length* 5)
+
+	;; Now that we use the byte compiler for macros,
+	;; interpreted /SHOW doesn't work until later in init.
+        #+sb-show (print "/hello, world!")
+
+        ;; Do warm init.
+	(let ((*print-length* 10)
 	      (*print-level* 5))
-          (sb!int:/show "about to LOAD warm.lisp")
+          #+sb-show (print "/about to LOAD warm.lisp")
 	  (load "src/cold/warm.lisp"))
-        (sb-int:/show "about to SAVE-LISP-AND-DIE")
+
+        ;; Unintern no-longer-needed stuff before the possible PURIFY
+        ;; in SAVE-LISP-AND-DIE.
+        #-sb-fluid (sb-impl::!unintern-init-only-stuff)
+
+	;; 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
 	;; wanted, it can easily be turned back on.)