1.0.43.34: differentiate cross-compiler output from target and host
authorNikodemus Siivola <nikodemus@random-state.net>
Thu, 7 Oct 2010 16:40:47 +0000 (16:40 +0000)
committerNikodemus Siivola <nikodemus@random-state.net>
Thu, 7 Oct 2010 16:40:47 +0000 (16:40 +0000)
 No difference in the end-product, but seeing "x-compiling" in
 build-logs makes them easier to read for slow people like me.

 That is:

 * while building the xc-host messages are from the host compiler.
   If the host happens to be SBCL, that means:

      ; compiling (DEFUN FOO ...)

 * while building the target:

      ; x-compiling (DEFUN FOO ...)

 * while building CLOS and contribs on target:

      ; compiling (DEFUN FOO ...)

make-host-2.lisp
src/compiler/main.lisp
version.lisp-expr

index 5af5a98..ab16fe5 100644 (file)
@@ -13,7 +13,7 @@
 
 (defun proclaim-target-optimization ()
   (let ((debug (if (position :sb-show *shebang-features*) 2 1)))
-    (sb-xc:proclaim
+    (proclaim
      `(optimize
        (compilation-speed 1) (debug ,debug)
        ;; CLISP's pretty-printer is fragile and tends to cause stack
index c0c6a81..33a1967 100644 (file)
@@ -1234,8 +1234,10 @@ Examples:
                  (*print-level* 2)
                  (*print-pretty* nil))
              (with-compiler-io-syntax
-                 (compiler-mumble "~&; ~:[compiling~;converting~] ~S"
-                                  *block-compile* form)))
+                 (compiler-mumble
+                  #-sb-xc-host "~&; ~:[compiling~;converting~] ~S"
+                  #+sb-xc-host "~&; ~:[x-compiling~;x-converting~] ~S"
+                  *block-compile* form)))
              form)
           ((and finalp
                 (eq :top-level-forms *compile-print*)
index b0f1c21..56f29d7 100644 (file)
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.43.33"
+"1.0.43.34"