X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=build-order.lisp-expr;h=3b5b727dc05be89f091a5b9668b5afd58dc9b6e6;hb=b282ecc0240c6dc67aaeea2d64046d411738385a;hp=55a52cfc8a0ac2170a5549ea8cebc1d20be9d1fd;hpb=403bacffd903f8c5787a182f4133cffc69b55dc0;p=sbcl.git

diff --git a/build-order.lisp-expr b/build-order.lisp-expr
index 55a52cf..3b5b727 100644
--- a/build-order.lisp-expr
+++ b/build-order.lisp-expr
@@ -75,15 +75,18 @@
  ("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/cross-thread" :not-target)
  ("src/code/cross-make-load-form" :not-target)
 
  ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
  ;;; stuff needed early both in cross-compilation host and in target Lisp
 
  ("src/code/uncross")
+ ("src/code/primordial-type")
  ("src/code/early-defbangmethod")
 
  ("src/code/defbangtype")
@@ -158,6 +161,7 @@
 
  ("src/code/target-error" :not-host)
 
+ ("src/compiler/early-backend")
  ;; 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
@@ -187,7 +191,8 @@
  ("src/code/misc-aliens" :not-host)
 
  ("src/code/array"         :not-host)
- ("src/code/target-sxhash" :not-host)
+ ("src/code/early-float"   :not-host)
+ ("src/code/target-sxhash" :not-host) ; needs most-fooative-foo-float constants
 
  ("src/code/list"   :not-host)
  ("src/code/seq"    :not-host) ; "code/seq" should come after "code/list".
@@ -412,6 +417,7 @@
  ("src/code/hash-table")
  ("src/code/readtable")
  ("src/code/pathname")
+ ("src/code/host-pprint")
  ("src/compiler/lexenv")
 
  ;; KLUDGE: Much stuff above here is the type system and/or the INFO
@@ -441,7 +447,6 @@
  ;; (and so that they don't cause lots of annoying compiler warnings
  ;; about undefined types). 
  ("src/compiler/generic/core")
- ("src/code/cross-thread" :not-target)
  ("src/code/thread")
  ("src/code/load")
 
@@ -474,6 +479,7 @@
  ("src/compiler/float-tran")
  ("src/compiler/saptran")
  ("src/compiler/srctran")
+ ("src/compiler/generic/vm-tran")
  ("src/compiler/locall")
  ("src/compiler/dfo")
  ("src/compiler/checkgen")
@@ -511,10 +517,24 @@
  ("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")
@@ -529,21 +549,7 @@
  ("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")
 
@@ -580,7 +586,6 @@
 
  ("src/compiler/copyprop")
  ("src/compiler/represent")
- ("src/compiler/generic/vm-tran")
  ("src/compiler/pack")
  ("src/compiler/codegen")
  ("src/compiler/debug")
@@ -612,6 +617,7 @@
  ("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