X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcold%2Fdefun-load-or-cload-xcompiler.lisp;h=cadc1b9d763bc69f747093d26897540533af73dd;hb=3eb39e017e52b5d704e7d33405c873af52a533fd;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..cadc1b9 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.
@@ -91,6 +89,7 @@
 		    ;; everything else which needs a separate
                     ;; existence in xc and target
 		    "BUILT-IN-CLASS"
+		    "BYTE" "BYTE-POSITION" "BYTE-SIZE"
 		    "CLASS" "CLASS-NAME" "CLASS-OF"
 		    "COMPILE-FILE"
 		    "COMPILE-FILE-PATHNAME"
@@ -104,14 +103,17 @@
 		    "DEFINE-MODIFY-MACRO"
 		    "DEFINE-SETF-EXPANDER"
 		    "DEFMACRO" "DEFSETF" "DEFSTRUCT" "DEFTYPE"
+		    "DEPOSIT-FIELD" "DPB"
 		    "FBOUNDP" "FDEFINITION" "FMAKUNBOUND"
 		    "FIND-CLASS"
 		    "GET-SETF-EXPANSION"
-		    "LAMBDA-LIST-KEYWORDS"
+		    "LDB" "LDB-TEST"
 		    "LISP-IMPLEMENTATION-TYPE" "LISP-IMPLEMENTATION-VERSION"
 		    "MACRO-FUNCTION"
 		    "MACROEXPAND" "MACROEXPAND-1" "*MACROEXPAND-HOOK*"
 		    "MAKE-LOAD-FORM"
+		    "MAKE-LOAD-FORM-SAVING-SLOTS"
+		    "MASK-FIELD"
 		    "PACKAGE" "PACKAGEP"
 		    "PROCLAIM"
 		    "SPECIAL-OPERATOR-P"
@@ -121,8 +123,37 @@
 		    "TYPE-OF" "TYPEP"
 		    "WITH-COMPILATION-UNIT"))
       (export (intern name package-name) package-name)))
-
-  (format t "~&/made SB-XC~%") ; REMOVEME
+  ;; don't watch:
+  (dolist (package-name '("SB!ALIEN"
+			  "SB!ALIEN-INTERNALS"
+			  "SB!ASSEM"
+			  "SB!BIGNUM"
+			  "SB!C"
+			  "SB!DEBUG"
+			  "SB!DI"
+			  "SB!DISASSEM"
+			  #!+sb-dyncount "SB!DYNCOUNT"
+			  "SB!FASL"
+			  "SB!IMPL"
+			  "SB!EXT"
+			  "SB!FORMAT"
+			  "SB!GRAY"
+			  "SB!INT"
+			  "SB!KERNEL"
+			  "SB!LOOP"
+			  #!+mp "SB!MP"
+			  "SB!PCL"
+			  "SB!PRETTY"
+			  "SB!PROFILE"
+			  "SB!SYS"
+			  "SB!UNIX"
+			  "SB!VM"
+			  "SB!WALKER"))
+    (shadowing-import (mapcar (lambda (name) (find-symbol name "SB-XC"))
+			      '("BYTE" "BYTE-POSITION" "BYTE-SIZE"
+				"DPB" "LDB" "LDB-TEST"
+				"DEPOSIT-FIELD" "MASK-FIELD"))
+		      package-name))
 
   ;; Build a version of Python to run in the host Common Lisp, to be
   ;; used only in cross-compilation.
@@ -134,13 +165,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 +179,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))