;; that they can handle the change. -- WHN 19990919
("src/code/defsetfs")
+ ("src/code/cold-init-helper-macros")
+
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;; cross-compiler-only replacements for stuff which in target Lisp would be
;;; supplied by basic machinery
("src/code/cross-misc" :not-target)
+ ("src/code/cross-char" :not-target)
("src/code/cross-byte" :not-target)
+ ("src/code/cross-boole" :not-target)
("src/code/cross-float" :not-target)
("src/code/cross-io" :not-target)
("src/code/cross-sap" :not-target)
("src/code/primordial-extensions")
+ ;; comes early so that stuff can reason about function names
+ ("src/code/function-names")
+
;; for various constants e.g. SB!XC:MOST-POSITIVE-FIXNUM and
;; SB!VM:N-LOWTAG-BITS, needed by "early-objdef" and others
("src/compiler/generic/early-vm")
;; mostly needed by stuff from comcom, but also used by "x86-vm"
("src/code/debug-var-io")
- ("src/code/cold-init-helper-macros")
-
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;; basic machinery for the target Lisp. Note that although most of these
;;; files are flagged :NOT-HOST, a few might not be.
;; in class.lisp.
("src/code/condition" :not-host)
+ ("src/compiler/generic/vm-array")
("src/compiler/generic/primtype")
;; the implementation of the compiler-affecting part of forms like
("src/code/cross-type" :not-target)
("src/compiler/generic/vm-type")
("src/compiler/proclaim")
+
+ ("src/code/class-init")
("src/code/typecheckfuns")
;; The DEFSTRUCT machinery needs SB!XC:SUBTYPEP, defined in
("src/compiler/compiler-error")
("src/code/type-init")
+ ;; Now that the type system is initialized, fix up UNKNOWN types that
+ ;; have crept in.
+ ("src/compiler/fixup-type")
;; These define target types needed by fndb.lisp.
("src/code/package")
("src/compiler/main") ; needs DEFSTRUCT FASL-OUTPUT from dump.lisp
("src/compiler/target-main" :not-host)
("src/compiler/ir1tran")
+ ("src/compiler/ir1tran-lambda")
("src/compiler/ir1-translators")
("src/compiler/ir1util")
("src/compiler/ir1report")
("src/compiler/float-tran")
("src/compiler/saptran")
("src/compiler/srctran")
+ ("src/compiler/generic/vm-tran")
("src/compiler/locall")
("src/compiler/dfo")
("src/compiler/checkgen")
("src/compiler/target/memory")
("src/compiler/target/static-fn")
("src/compiler/target/arith"
- ;; KLUDGE: for ppc and sparc this appears to be necessary -- see the
- ;; comment below regarding src/compiler/target/array -- CSR,
- ;; 2002-05-05
- :ignore-failure-p)
+ ;; KLUDGE: for ppc and sparc this appears to be necessary, as it
+ ;; used to be for array VOPs for X86 until ca. 0.8.5.24 when CSR's
+ ;; patch for that architecture was finally committed
+ ;;
+ ;; old (0.8.5.23) comment on the array-VOP hack for X86:
+ ;; x Compiling this file for X86 raises alarming warnings of
+ ;; x the form
+ ;; x Argument FOO to VOP CHECK-BOUND has SC restriction
+ ;; x DESCRIPTOR-REG which is not allowed by the operand type:
+ ;; x (:OR POSITIVE-FIXNUM)
+ ;; x This seems not to be something that I broke, but rather a "feature"
+ ;; x inherited from classic CMU CL. (Debian cmucl_2.4.8.deb compiling
+ ;; x Debian cmucl_2.4.8.tar.gz raises the same warning). Thus, even though
+ ;; x these warnings are severe enough that they would ordinarily abort
+ ;; x compilation, for now we blithely ignore them and press on to more
+ ;; x pressing problems. Someday, though, it would be nice to figure out
+ ;; x what the problem is and fix it.
+ #!+(or ppc sparc) :ignore-failure-p)
("src/compiler/target/subprim")
("src/compiler/target/debug")
("src/compiler/early-aliencomp")
("src/compiler/target/c-call")
("src/compiler/target/cell")
- ("src/code/late-symbol" :not-host)
("src/compiler/target/values")
("src/compiler/target/alloc")
("src/compiler/target/call")
("src/compiler/target/nlx")
("src/compiler/generic/late-nlx")
("src/compiler/target/show")
- ("src/compiler/target/array"
- ;; KLUDGE: Compiling this file for X86 raises alarming warnings of
- ;; the form
- ;; Argument FOO to VOP CHECK-BOUND has SC restriction
- ;; DESCRIPTOR-REG which is not allowed by the operand type:
- ;; (:OR POSITIVE-FIXNUM)
- ;; This seems not to be something that I broke, but rather a "feature"
- ;; inherited from classic CMU CL. (Debian cmucl_2.4.8.deb compiling
- ;; Debian cmucl_2.4.8.tar.gz raises the same warning). Thus, even though
- ;; these warnings are severe enough that they would ordinarily abort
- ;; 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. (See the comments in
- ;; src/compiler/x86/array for a candidate patch.) -- WHN 19990323
- :ignore-failure-p)
+ ("src/compiler/target/array")
("src/compiler/generic/array")
("src/compiler/target/pred")
("src/compiler/copyprop")
("src/compiler/represent")
- ("src/compiler/generic/vm-tran")
("src/compiler/pack")
("src/compiler/codegen")
("src/compiler/debug")
("src/code/target-random" :not-host) ; needs "code/random"
("src/code/target-hash-table" :not-host) ; needs "code/hash-table"
("src/code/reader" :not-host) ; needs "code/readtable"
+ ("src/code/target-stream" :not-host) ; needs WHITESPACEP from "code/reader"
("src/code/target-pathname" :not-host) ; needs "code/pathname"
("src/code/filesys" :not-host) ; needs HOST from "code/pathname"
("src/code/save" :not-host) ; uses the definition of PATHNAME
;; DEFVAR or DEFPARAMETER.
("src/code/cl-specials")
+ ;; FIXME: here? earlier? can probably be as late as possible. Also
+ ;; maybe call it FORCE-DELAYED-PROCLAIMS?
+ ("src/compiler/late-proclaim")
+
;; fundamental target macros (e.g. CL:DO and CL:DEFUN) and support
;; for them
("src/code/defboot")
projects / sbcl.git / blobdiff