0.7.11.2:

[sbcl.git] / make-target-2.sh

diff --git a/make-target-2.sh b/make-target-2.sh
index 58bd723..0a51ab9 100644 (file)
--- a/make-target-2.sh
+++ b/make-target-2.sh
@@ -42,6 +42,7 @@ echo //doing warm init
         ;; 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")
@@ -56,6 +57,7 @@ echo //doing warm init
        ;; 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?
@@ -65,6 +67,17 @@ echo //doing warm init
          (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