("code/target-c-call" :not-host)
("code/target-allocate" :not-host)
+ ("code/misc-aliens" :not-host) ; needs DEF-ALIEN-ROUTINE from target-alieneval
+
("code/array" :not-host)
("code/target-sxhash" :not-host)
("code/float" :not-host)
("code/irrat" :not-host)
- ("code/char" :not-host)
+ ("code/char")
+ ("code/target-char" :not-host)
("code/target-misc" :not-host)
("code/misc")
; from "code/pathname"
("code/sharpm" :not-host) ; uses stuff from "code/reader"
- ;; stuff for byte compilation. This works only in the target system,
- ;; because fundamental BYTE-FUNCTION-OR-CLOSURE types are implemented
- ;; as nonportable FUNCALLABLE-INSTANCEs.
+ ;; stuff for byte compilation. Note that although byte code is
+ ;; "portable", it'd be hard to make it work on the cross-compilation
+ ;; host, because fundamental BYTE-FUNCTION-OR-CLOSURE types are
+ ;; implemented as FUNCALLABLE-INSTANCEs, and it's not obvious
+ ;; how to emulate those in a vanilla ANSI Common Lisp.
("code/byte-types" :not-host)
("compiler/byte-comp")
("compiler/target-byte-comp" :not-host)
- ;; FIXME: Could byte-interp be moved here? It'd be logical..
+ ("code/byte-interp" :not-host) ; needs *SYSTEM-CONSTANT-CODES* from byte-comp
;; defines SB!DI:DO-DEBUG-FUNCTION-BLOCKS, needed by target-disassem.lisp
("code/debug-int" :not-host)
("code/bit-bash" :not-host) ; needs %NEGATE from assembly/target/arith
- ("code/byte-interp" :not-host) ; needs *SYSTEM-CONSTANT-CODES* from byte-comp
-
("code/target-load" :not-host) ; needs specials from code/load.lisp
;; FIXME: Does this really need stuff from compiler/dump.lisp?