X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcold%2Fdefun-load-or-cload-xcompiler.lisp;h=3445a066ee26b2106f433b3b501704e79d5db501;hb=8a3bbf707f43fd95bc3025e3f222563c36b599fd;hp=2a178e0a9bea19af9db9a7944aeab2b38fa5eabe;hpb=7dd568fb64927be78556ac27f1f0dc60e79cf942;p=sbcl.git

diff --git a/src/cold/defun-load-or-cload-xcompiler.lisp b/src/cold/defun-load-or-cload-xcompiler.lisp
index 2a178e0..3445a06 100644
--- a/src/cold/defun-load-or-cload-xcompiler.lisp
+++ b/src/cold/defun-load-or-cload-xcompiler.lisp
@@ -13,8 +13,6 @@
 ;;; cross-compilation host Common Lisp.
 (defun load-or-cload-xcompiler (load-or-cload-stem)
 
-  (format t "~&/entering LOAD-OR-CLOAD-XCOMPILER~%") ; REMOVEME
-
   ;; The running-in-the-host-Lisp Python cross-compiler defines its
   ;; own versions of a number of functions which should not overwrite
   ;; host-Lisp functions. Instead we put them in a special package.
@@ -107,7 +105,6 @@
 		    "FBOUNDP" "FDEFINITION" "FMAKUNBOUND"
 		    "FIND-CLASS"
 		    "GET-SETF-EXPANSION"
-		    "LAMBDA-LIST-KEYWORDS"
 		    "LISP-IMPLEMENTATION-TYPE" "LISP-IMPLEMENTATION-VERSION"
 		    "MACRO-FUNCTION"
 		    "MACROEXPAND" "MACROEXPAND-1" "*MACROEXPAND-HOOK*"
@@ -122,8 +119,6 @@
 		    "WITH-COMPILATION-UNIT"))
       (export (intern name package-name) package-name)))
 
-  (format t "~&/made SB-XC~%") ; REMOVEME
-
   ;; Build a version of Python to run in the host Common Lisp, to be
   ;; used only in cross-compilation.
   ;;
@@ -134,13 +129,10 @@
   ;; order to make the compiler aware of the definitions of assembly
   ;; routines.
   (do-stems-and-flags (stem flags)
-    (format t "~&/STEM=~S FLAGS=~S~%" stem flags) ; REMOVEME
     (unless (find :not-host flags)
-      (format t "~&/FUNCALLing ~S~%" load-or-cload-stem) ; REMOVEME
       (funcall load-or-cload-stem
 	       stem
 	       :ignore-failure-p (find :ignore-failure-p flags))
-      (format t "~&/back from FUNCALL~%") ; REMOVEME
       #!+sb-show (warn-when-cl-snapshot-diff *cl-snapshot*)))
 
   ;; If the cross-compilation host is SBCL itself, we can use the
@@ -151,7 +143,6 @@
   ;; (in the ordinary build procedure anyway) essentially everything
   ;; which is reachable at this point will remain reachable for the
   ;; entire run.
-  (format t "~&/doing PURIFY~%") ; REMOVEME
   #+sbcl (sb-ext:purify)
 
   (values))