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 ...)
(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
(*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*)
;;; 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"