0.6.11.40:

[sbcl.git] / stems-and-flags.lisp-expr

diff --git a/stems-and-flags.lisp-expr b/stems-and-flags.lisp-expr
index cf2577b..12a5946 100644 (file)
--- a/stems-and-flags.lisp-expr
+++ b/stems-and-flags.lisp-expr
@@ -172,6 +172,8 @@
  ("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)
 
@@ -213,7 +215,8 @@
  ("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")
 
@@ -569,12 +572,12 @@
  ;; 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 make those portable.
+ ;; 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)
@@ -595,8 +598,6 @@
 
  ("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?