X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcold%2Fshared.lisp;h=3c910ac7e1ffe58b2bddb40cdf0eef83ba4e6033;hb=4cf50b1896b25f5337e7c258b0b560da00d47993;hp=75a3b0470486a16c0dcc858ec1f8859bad2580d3;hpb=334af30b26555f0bf706f7157b399bdbd4fad548;p=sbcl.git

diff --git a/src/cold/shared.lisp b/src/cold/shared.lisp
index 75a3b04..3c910ac 100644
--- a/src/cold/shared.lisp
+++ b/src/cold/shared.lisp
@@ -15,12 +15,19 @@
 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
 ;;;; files for more information.
 
-;;; TO DO: Might it be possible to increase the efficiency of CMU CL's garbage
-;;; collection on my large (256Mb) machine by doing larger incremental GC steps
-;;; than the default 2 Mb of CMU CL 2.4.9? A quick test 19990729, setting this
-;;; to 5E6 showed no significant improvement, but it's possible that more
-;;; cleverness might help..
-;#+cmu (setf ext:*bytes-consed-between-gcs* (* 5 (expt 10 6)))
+;;; GC tuning has little effect on the x86 due to the generational
+;;; collector.  For the older stop & copy collector, it assuredly
+;;; does.  GC time is proportional to the amount of non-grabage
+;;; needing collection and copying; when the application involved is
+;;; the SBCL compiler, it doesn't take any longer to collect 20Mb than
+;;; 2              -dan, 20000819
+
+#+sbcl
+(progn
+  (sb-ext:gc-off)
+  (setf sb-KERNEL::*bytes-consed-between-gcs* (* 20 (expt 10 6)))
+  (sb-ext:gc-on)
+  (sb-ext:gc))
 
 ;;; FIXME: I'm now inclined to make all the bootstrap stuff run in CL-USER
 ;;; instead of SB-COLD. If I do so, I should first take care to
@@ -30,11 +37,6 @@
 (defpackage "SB-COLD" (:use "CL"))
 (in-package "SB-COLD")
 
-;;; prefix for source filename stems when cross-compiling
-(defvar *src-prefix* "src/")
-;;; (We don't bother to specify the source suffix here because ".lisp" is such
-;;; a good default value that we never have to specify it explicitly.)
-
 ;;; prefixes for filename stems when cross-compiling. These are quite arbitrary
 ;;; (although of course they shouldn't collide with anything we don't want to
 ;;; write over). In particular, they can be either relative path names (e.g.
@@ -306,7 +308,6 @@
   (load (in-host-compilation-mode
 	  (lambda ()
 	    (compile-stem stem
-			  :src-prefix *src-prefix*
 			  :obj-prefix *host-obj-prefix*
 			  :obj-suffix *host-obj-suffix*
 			  :compile-file #'cl:compile-file
@@ -332,7 +333,6 @@
   (funcall *in-target-compilation-mode-fn*
 	   (lambda ()
 	     (compile-stem stem
-			   :src-prefix *src-prefix*
 			   :obj-prefix *target-obj-prefix*
 			   :obj-suffix *target-obj-suffix*
 			   :ignore-failure-p ignore-failure-p