[9a2d58]: stems-and-flags.lisp-expr  Maximize  Restore  History

Download this file

644 lines (496 with data), 23.1 kB

;;;; -*- Lisp -*-
;;;; build order

;;;; This software is part of the SBCL system. See the README file for
;;;; more information.
;;;; This software is derived from the CMU CL system, which was
;;;; written at Carnegie Mellon University and released into the
;;;; public domain. The software is in the public domain and is
;;;; provided with absolutely no warranty. See the COPYING and CREDITS
;;;; files for more information.

;;; This is a linear ordering of system sources which works both to
;;; compile/load the cross-compiler under the host Common Lisp and to
;;; cross-compile the compiler into the under-construction target
;;; Common Lisp.
;;; Of course, it'd be very nice to have this be a dependency DAG
;;; instead, so that we could do automated incremental recompilation.
;;; But the dependencies are varied and subtle, and it'd be extremely
;;; difficult to extract them automatically, and it'd be extremely
;;; tedious and error-prone to extract them manually, so we don't 
;;; extract them. (It would be nice to fix this someday. The most
;;; feasible approach that I can think of would be to make the
;;; dependencies work on a package level, not an individual file
;;; level. Doing it at the package level would make the granularity
;;; coarse enough that it would probably be pretty easy to maintain
;;; the dependency information manually, and the brittleness of the
;;; package system would help make most violations of the declared
;;; dependencies obvious at build time. -- WHN 20000803
;;; 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?
 ;;; miscellaneous

 ;; This comes early because it's useful for debugging everywhere.

 ;; This comes early because the cross-compilation host's backquote logic
 ;; expand into something which can't be executed on the target Lisp (e.g.
 ;; in CMU CL where it expands into internal functions like BACKQ-LIST), and
 ;; by replacing the host backquote logic with our own as early as possible,
 ;; we minimize the chance of any forms referring to host Lisp internal
 ;; functions leaking into target Lisp code.

 ;; various DEFSETFs and/or other DEFMACROish things, defined as early as
 ;; possible so we don't need to fiddle with any subtleties of defining them
 ;; before any possible use

 ;; KLUDGE: It would be nice to reimplement most or all of these as
 ;; functions (possibly inlined functions) so that we wouldn't need to
 ;; worry so much about forcing them all to be defined before any possible
 ;; use. It might be pretty tedious, though, working through any
 ;; transforms and translators and optimizers and so forth to make sure
 ;; that they can handle the change. -- WHN 19990919

 ;;; 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-float" :not-target)
 ("src/code/cross-io"    :not-target)
 ("src/code/cross-sap"   :not-target)

 ;;; stuff needed early both in cross-compilation host and in target Lisp




 ;; for various constants e.g. SB!VM:*TARGET-MOST-POSITIVE-FIXNUM* and
 ;; SB!VM:LOWTAG-BITS, needed by "early-objdef" and others
 ("src/code/early-array") ; needs "early-vm" numbers

 ("src/code/parse-body")      ; on host for PARSE-BODY
 ("src/code/parse-defmacro")  ; on host for PARSE-DEFMACRO
 ("src/code/extensions")      ; on host for COLLECT, SYMBOLICATE, etc.
 ("src/compiler/deftype")     ; on host for SB!XC:DEFTYPE
 ("src/code/early-alieneval") ; for vars needed both at build and run time



 ;; mostly needed by stuff from comcom, but also used by "x86-vm"


 ;;; basic machinery for the target Lisp. Note that although most of these
 ;;; files are flagged :NOT-HOST, a few might not be.

 ("src/code/target-defbangmethod" :not-host)

 ("src/code/early-print" :not-host)
 ("src/code/early-pprint" :not-host)
 ("src/code/early-impl" :not-host)

 ("src/code/target-extensions" :not-host)

 ("src/code/early-defstructs" :not-host) ; gotta-be-first DEFSTRUCTs


 ;; This needs DEF!STRUCT, and is itself needed early so that structure
 ;; accessors and inline functions defined here can be compiled inline
 ;; later. (Avoiding full calls not only increases efficiency, but also
 ;; avoids some cold init issues involving full calls to structure
 ;; accessors.)

 ("src/code/pcounter" :not-host)

 ("src/code/lisp-stream" :not-host)

 ("src/code/sysmacs" :not-host)

 ;; "assembly/assemfile" was here in the sequence inherited from
 ;; CMU CL worldcom.lisp, but also appears later in the sequence
 ;; inherited from CMU CL comcom.lisp. We shouldn't need two versions,
 ;; so I've deleted the one here. -- WHN 19990620

 ;; FIXME: There are lots of "maybe" notes in this file, e.g.
 ;; "maybe should be :BYTE-COMPILE T". Once the system is stable,
 ;; look into them.

 ("src/code/early-target-error" :not-host) ; maybe should be :BYTE-COMPILE T
 ;; FIXME: maybe should be called "target-error", with "late-target-error"
 ;; called "condition"

 ;; a comment from classic CMU CL:
 ;;   "These guys can supposedly come in any order, but not really.
 ;;    Some are put at the end so that macros don't run interpreted
 ;;    and stuff."
 ;; Dunno exactly what this meant or whether it still holds. -- WHN 19990803
 ;; FIXME: more informative and up-to-date comment?
 ("src/code/globals"     :not-host)
 ("src/code/kernel"      :not-host)
 ("src/code/toplevel"    :not-host)
 ("src/code/cold-error"  :not-host)
 ("src/code/fdefinition" :not-host)
 ;; FIXME: Figure out some way to make the compiler macro for INFO 
 ;; available for compilation of "code/fdefinition".

 ;; In classic CMU CL, code/type was here. I've since split that into
 ;; lots of smaller pieces, some of which are here and some of which
 ;; are handled later in the sequence, when the cross-compiler is
 ;; built. -- WHN 19990620
 ("src/code/target-type" :not-host)

 ("src/code/pred" :not-host)

 ("src/code/target-alieneval" :not-host)
 ("src/code/target-c-call"    :not-host)
 ("src/code/target-allocate"  :not-host)

 ;; This needs DEF-ALIEN-ROUTINE from target-alieneval.
 ("src/code/misc-aliens" :not-host)

 ("src/code/array"         :not-host)
 ("src/code/target-sxhash" :not-host)

 ("src/code/list"   :not-host)
 ("src/code/seq"    :not-host) ; "code/seq" should come after "code/list".
 ("src/code/coerce" :not-host)

 ("src/code/string"     :not-host)
 ("src/code/mipsstrops" :not-host)

 ;; "src/code/unix.lisp" needs this. It's generated automatically by
 ;; grovel_headers.c, i.e. it's not in CVS.
 ("output/stuff-groveled-from-headers" :not-host)

 ("src/code/unix" :not-host)

 #!+mach  ("src/code/mach"     :not-host)
 #!+mach  ("src/code/mach-os"  :not-host)
 #!+sunos ("src/code/sunos-os" :not-host)
 #!+hpux  ("src/code/hpux-os"  :not-host)
 #!+osf1  ("src/code/osf1-os"  :not-host)
 #!+irix  ("src/code/irix-os"  :not-host)
 #!+bsd   ("src/code/bsd-os"   :not-host)
 #!+linux ("src/code/linux-os" :not-host)

 ;; KLUDGE: I'd prefer to have this done with a "code/target" softlink
 ;; instead of a bunch of reader macros. -- WHN 19990308
 #!+pmax ("src/code/pmax-vm" :not-host)
 #!+(and sparc svr4) ("src/code/sparc-svr4-vm" :not-host)
 #!+(and sparc (not svr4)) ("src/code/sparc-vm" :not-host)
 #!+rt    ("src/code/rt-vm"    :not-host)
 #!+hppa  ("src/code/hppa-vm"  :not-host)
 #!+x86   ("src/code/x86-vm"   :not-host)
 #!+alpha ("src/code/alpha-vm" :not-host)
 #!+sgi   ("src/code/sgi-vm"   :not-host)

 ("src/code/target-signal" :not-host) ; needs OS-CONTEXT-T from x86-vm

 ("src/code/symbol"         :not-host)
 ("src/code/bignum"         :not-host)
 ("src/code/target-numbers" :not-host)
 ("src/code/float-trap"     :not-host)
 ("src/code/float"          :not-host)
 ("src/code/irrat"          :not-host)

 ("src/code/target-char" :not-host)
 ("src/code/target-misc" :not-host)

 #!-gengc ("src/code/room"   :not-host)
 #!-gengc ("src/code/gc"     :not-host)
 #!-gengc ("src/code/purify" :not-host)

 #!+gengc ("src/code/gengc" :not-host)

 ("src/code/stream"        :not-host)
 ("src/code/print"         :not-host)
 ("src/code/pprint"        :not-host) ; maybe should be :BYTE-COMPILE T
 ("src/code/target-format" :not-host) ; maybe should be :BYTE-COMPILE T
 ("src/code/defpackage"    :not-host)
 ("src/code/pp-backq"      :not-host) ; maybe should be :BYTE-COMPILE T

 ("src/code/error-error" :not-host) ; needs WITH-STANDARD-IO-SYNTAX macro

 ("src/code/serve-event" :not-host)
 ("src/code/fd-stream"   :not-host)

 ("src/code/module" :not-host) ; maybe should be :BYTE-COMPILE T


 ("src/code/target-eval" :not-host) ; FIXME: uses INFO, wants compiler macro

 ("src/code/interr" :not-host)

 ("src/code/query"  :not-host) ; maybe should be :BYTE-COMPILE T

 ("src/code/sort"  :not-host)
 ("src/code/time"  :not-host)
 ("src/code/weak"  :not-host)
 ("src/code/final" :not-host)

 #!+mp ("src/code/multi-proc" :not-host)

 ("src/code/setf-funs" :not-host)

 ;;; compiler (and a few miscellaneous files whose dependencies make it
 ;;; convenient to stick them here)



 ;; ("src/code/defbangmacro" was here until sbcl-


 ;; needed by "compiler/vop"

 ;; for e.g. BLOCK-ANNOTATION, needed by "compiler/vop"

 ;; for e.g. PRIMITIVE-TYPE, needed by "vmdef"

 ;; needed by "vm" and "primtype"

 ;; for e.g. MAX-VOP-TN-REFS, needed by "meta-vmdef"

 ;; needs "backend"

 ;; for INFO and SB!XC:MACRO-FUNCTION, needed by defmacro.lisp



 ;; for e.g. !DEF-PRIMITIVE-TYPE, needed by primtype.lisp, and
 ;; DEFINE-STORAGE-CLASS, needed by target/vm.lisp

 ;; for e.g. DESCRIPTOR-REG, needed by primtype.lisp

 ;; for e.g. SPECIFIER-TYPE, needed by primtype.lisp

 ;; FIXME: Classic CMU CL had SAFETY 2 DEBUG 2 set around the compilation
 ;; of "code/class". Why?

 ;; The definitions for CONDITION and CONDITION-CLASS depend on
 ;; SLOT-CLASS, defined in classes.lisp.
 ("src/code/late-target-error" :not-host) ; FIXME: maybe should be :BYTE-COMPILE T


 ;; the implementation of the compiler-affecting part of forms like
 ;; DEFMACRO and DEFTYPE; must be loaded before we can start
 ;; defining types

 ;; for DEFSTRUCT ALIEN-TYPE, needed by host-type.lisp

 ;; can't be done until definition of e.g. DEF-ALIEN-TYPE-CLASS in
 ;; host-alieneval.lisp

 ;; SB!XC:DEFTYPE is needed in order to compile late-type
 ;; in the host Common Lisp, and in order to run, it needs

 ;; These appear here in the build sequence because they require
 ;;   * the macro INFO, defined in globaldb.lisp, and
 ;;   * the function PARSE-DEFMACRO, defined in parse-defmacro.lisp,
 ;; and because they define
 ;;   * the function SPECIFIER-TYPE, which is used in fndb.lisp.

 ;; The inline definition of TYPEP-TO-LAYOUT here needs inline
 ;; functions defined in classes.lisp, and is needed in turn by
 ;; the target version of "code/defstruct".
 ("src/code/target-defstruct" :not-host)

 ;; stuff needed by "code/defstruct"
 ("src/code/cross-type" :not-target)

 ;; The DEFSTRUCT machinery needs SB!XC:SUBTYPEP, defined in 
 ;; "code/late-type", and SB!XC:TYPEP, defined in "code/cross-type",
 ;; and SPECIALIZE-ARRAY-TYPE, defined in "compiler/generic/vm-type".

 ;; ALIEN-VALUE has to be defined as a class (done by DEFSTRUCT
 ;; machinery) before we can set its superclasses here.


 ;; needs IR1-ATTRIBUTES macro, defined in knownfun.lisp

 ;; This needs not just the SB!XC:DEFSTRUCT machinery, but also
 ;; the TYPE= stuff defined in late-type.lisp, and the
 ;; CHECK-FUNCTION-NAME defined in proclaim.lisp.




 ;; These define target types needed by fndb.lisp.

 ;; KLUDGE: Much stuff above here is the type system and/or the INFO
 ;; system, not really the compiler proper. It might be easier to
 ;; understand the system if those things were split off into packages
 ;; SB-TYPE and SB-INFO and built in their own sections. -- WHN 20000124

 ;; In classic CMU CL (re)build order, these were done later, but
 ;; in building from scratch, these must be loaded before
 ;; "compiler/generic/objdef" in order to allow forms like
 ;; (DEFINE-PRIMITIVE-OBJECT (..) (CAR ..) ..) to work.




 ;; This has ASSEMBLY-UNIT-related stuff needed by core.lisp.

 ;; core.lisp contains DEFSTRUCT CORE-OBJECT, and "compiler/main.lisp"
 ;; does lots of (TYPEP FOO 'CORE-OBJECT), so it's nice to compile this
 ;; before "compiler/main.lisp" so that those can be coded efficiently
 ;; (and so that they don't cause lots of annoying compiler warnings
 ;; about undefined types). 


 ("src/code/fop") ; needs macros from code/host-load.lisp


 ("src/compiler/trace-table") ; needs EMIT-LABEL macro from compiler/assem.lisp

 ;; Compiling this requires fop definitions from code/fop.lisp and
 ;; trace table definitions from compiler/trace-table.lisp.

 ("src/compiler/main") ; needs DEFSTRUCT FASL-OUTPUT from dump.lisp
 ("src/compiler/target-main" :not-host)

 ;; Compiling this file requires the macros SB!ASSEM:EMIT-LABEL and
 ;; SB!ASSEM:EMIT-POST-IT, defined in assem.lisp.





 ("src/compiler/fixup") ; for DEFSTRUCT FIXUP, used by insts.lisp




  ;; KLUDGE: Compiling this file 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:
  ;; 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.. -- WHN 19990323

 ("src/assembly/target/assem-rtns" :assem)
 ("src/assembly/target/array"      :assem)
 ("src/assembly/target/arith"      :assem)
 ("src/assembly/target/alloc"      :assem)




 ;; KLUDGE: This has #!+GENGC things in it which are intended to
 ;; overwrite code in ir2tran.lisp, so it has to come after ir2tran.lisp.
 ;; FIXME: Those things should probably be ir2tran.lisp instead, and the
 ;; things they now overwrite should instead be #!-GENGC so they're never
 ;; generated in the first place.


 #!+sb-dyncount ("src/compiler/dyncount")
 #!+sb-dyncount ("src/code/dyncount")

 ;; needed by OPEN-FASL-OUTPUT, which is called by COMPILE-FILE

 ;; needed by various unhappy-path cases in the cross-compiler

 ;; This wasn't in classic CMU CL "comcom.lisp", but it has some stuff
 ;; that Python-as-cross-compiler has turned out to need.

 ;; files which are only needed in the target system, and/or which are
 ;; only possible in the target system, and which depend in some way 
 ;; (directly or indirectly) on stuff compiled as part of the compiler

 ("src/compiler/generic/target-core" :not-host) ; uses stuff from
                                            ;   "compiler/generic/core"

 ("src/code/target-sap"        :not-host) ; uses SAP-INT-TYPE
 ("src/code/target-package"    :not-host) ; needs "code/package"
 ("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-pathname"   :not-host) ; needs "code/pathname", maybe 
                                      ;   should be :BYTE-COMPILE T
 ("src/code/filesys"           :not-host) ; needs HOST from "code/pathname",
                                      ;   maybe should be :BYTE-COMPILE T
 ("src/code/save"              :not-host) ; uses the definition of PATHNAME
                                      ;   from "code/pathname"
 ("src/code/sharpm"            :not-host) ; uses stuff from "code/reader"

 ;; 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.
 ("src/code/byte-types" :not-host)
 ("src/compiler/target-byte-comp" :not-host)
 ("src/code/byte-interp" :not-host) ; needs byte-comp *SYSTEM-CONSTANT-CODES*

 ;; defines SB!DI:DO-DEBUG-FUNCTION-BLOCKS, needed by target-disassem.lisp
 ("src/code/debug-int" :not-host)

 ;; target-only assemblerish stuff
 ("src/compiler/target-disassem"     :not-host)
 ("src/compiler/target/target-insts" :not-host)

 ;; the IR1 interpreter (as opposed to the byte code interpreter)
 #!+sb-interpreter ("src/compiler/eval-comp" :not-host)
 #!+sb-interpreter ("src/compiler/eval"      :not-host)

 ("src/code/debug" :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*.
 ("src/code/parse-defmacro-errors" :not-host)

 ("src/code/bit-bash"    :not-host) ; needs %NEGATE from assembly/target/arith

 ("src/code/target-load" :not-host) ; needs specials from code/load.lisp

 ;; FIXME: Does this really need stuff from compiler/dump.lisp?
 ("src/compiler/target-dump" :not-host) ; needs stuff from compiler/dump.lisp

 ("src/code/cold-init" :not-host) ; needs (SETF EXTERN-ALIEN) macroexpansion

 ;; target macros and DECLAIMs installed at build-the-cross-compiler time

 ;; Declare all target special variables defined by ANSI now, so that
 ;; we don't have to worry about any of them being bound incorrectly
 ;; when the compiler processes code which appears before the appropriate

 ;; fundamental target macros (e.g. CL:DO and CL:DEFUN) and support
 ;; for them
 ;; FIXME: Since a lot of this code is just macros, perhaps it should be
 ;; byte compiled?


 ;; other target-code-building stuff which can't be processed until
 ;; machinery like SB!XC:DEFMACRO exists

 ("src/code/late-format") ; needs SB!XC:DEFMACRO
 ("src/code/sxhash") ; needs SB!XC:DEFINE-MODIFY-MACRO

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks