;;; FIXME: Perhaps now that a significant number of files are built
;;; in warm load instead of cold load, this file should now be called
;;; cold-stems-and-flags.lisp-expr? Also, perhaps this file should move
-;;; into the src/cold/ directory?
+;;; into the src/cold directory?
(
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;; miscellaneous
("code/uncross")
("code/early-defbangmethod")
+ ("code/defbangtype")
+ ("code/defbangmacro")
+
+ ("code/primordial-extensions")
+
+ ;; for various constants e.g. SB!VM:*TARGET-MOST-POSITIVE-FIXNUM* and
+ ;; SB!VM:LOWTAG-BITS, needed by "early-objdef" and others
+ ("compiler/generic/early-vm")
+ ("compiler/generic/early-objdef")
+ ("compiler/target/parms")
+ ("code/early-array") ; needs "early-vm" numbers
+
("code/parse-body") ; on host for PARSE-BODY
("code/parse-defmacro") ; on host for PARSE-DEFMACRO
- ("code/early-defboot") ; on host for FILE-COMMENT, DO-ANONYMOUS, etc.
("code/boot-extensions") ; on host for COLLECT etc.
("code/early-extensions") ; on host for SYMBOLICATE etc.
("code/late-extensions") ; FIXME: maybe no longer needed on host now that
("code/specializable-array")
- ;; for various constants e.g. SB!VM:*TARGET-MOST-POSITIVE-FIXNUM* and
- ;; SB!VM:LOWTAG-BITS, needed by "early-objdef" and others
- ("compiler/generic/early-vm")
- ("compiler/generic/early-vm-macs")
- ("compiler/generic/early-objdef")
- ("compiler/target/parms")
- ("code/early-array") ; needs "early-vm" numbers
("code/early-cl")
("code/early-load")
("code/target-alieneval" :not-host)
("code/target-c-call" :not-host)
- ("code/target-sap" :not-host)
+ ("code/target-allocate" :not-host)
("code/array" :not-host)
("code/target-sxhash" :not-host)
("code/setf-funs" :not-host)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
- ;;; compiler (and a few miscellaneous :NOT-HOST files whose
- ;;; dependencies make it convenient to stick them here)
-
-; replaced with defbangtype.lisp in sbcl-0.6.2
-; ;; There are some things (e.g. the type SB!KERNEL:INDEX) which are
-; ;; used early in the compiler in both host and target forms (i.e.
-; ;; SB!KERNEL:INDEX defined to cross-compilation host and
-; ;; SB!KERNEL:INDEX defined to cross-compiler itself).
-; ("code/early-ugly-duplicates")
-
- ("code/defbangtype")
+ ;;; compiler (and a few miscellaneous files whose dependencies make it
+ ;;; convenient to stick them here)
("compiler/early-c")
+ ("compiler/policy")
("code/numbers")
("code/typedefs")
- ("code/defbangmacro")
+ ;; ("code/defbangmacro" was here until sbcl-0.6.7.3.)
("compiler/macros")
("compiler/generic/vm-macs")
("compiler/late-macros")
- ;; for e.g. DEF-PRIMITIVE-TYPE, needed by primtype.lisp, and
+ ;; for e.g. !DEF-PRIMITIVE-TYPE, needed by primtype.lisp, and
;; DEFINE-STORAGE-CLASS, needed by target/vm.lisp
("compiler/meta-vmdef")
;; host-alieneval.lisp
("code/host-c-call")
- ;; SB!XC:DEFTYPE is needed in order to compile late-target-type
+ ;; SB!XC:DEFTYPE is needed in order to compile late-type
;; in the host Common Lisp, and in order to run, it needs
;; %COMPILER-DEFTYPE.
("compiler/compiler-deftype")
;; compilation, for now we blithely ignore them and press on to more
;; pressing problems. Someday, though, it would be nice to figure out
;; what the problem is and fix it.. -- WHN 19990323
- ;; FIXME: This problem doesn't seem to occur in the cross-compiler.
- ;; Check whether it occurs when compiling with the final target SBCL.
- ;; If it doesn't, we can punt the KLUDGE message.
:ignore-failure-p)
("compiler/target/pred")
("compiler/target/type-vops")
("compiler/generic/target-core" :not-host) ; uses stuff from
; "compiler/generic/core"
+ ("code/target-sap" :not-host) ; uses SAP-INT-TYPE
("code/target-package" :not-host) ; needs "code/package"
("code/target-random" :not-host) ; needs "code/random"
("code/target-hash-table" :not-host) ; needs "code/hash-table"
; 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 make those portable.
("code/byte-types" :not-host)
("compiler/byte-comp")
("compiler/target-byte-comp" :not-host)
#!+sb-interpreter ("compiler/eval" :not-host)
("code/debug" :not-host) ; maybe should be :BYTE-COMPILE T
- ;; FIXME: This has been moved to warm init, and should be deleted here.
- #+nil ("code/ntrace" :not-host) ; maybe should be :BYTE-COMPILE T
;; These can't be compiled until CONDITION and DEFINE-CONDITION
;; are defined, and they also use SB-DEBUG:*STACK-TOP-HINT*.
projects / sbcl.git / blobdiff