X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=da348e5ccaf01b45f8cfc734e23957eaf08d9701;hb=4a0ab5193096ca70dbbf43bb21418544f6d018b7;hp=5aa58f73a9f9f768c22de08febd5c395fcfc2fc6;hpb=dccfa0f4e378a267744c03b1416accdf9d888987;p=sbcl.git

diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr
index 5aa58f7..da348e5 100644
--- a/base-target-features.lisp-expr
+++ b/base-target-features.lisp-expr
@@ -64,59 +64,15 @@
  ;; the executable I'm running.
  :sb-doc
 
- ;; When this is set, EVAL is implemented as an "IR1 interpreter": 
- ;; code is compiled into the compiler's first internal representation,
- ;; then the IR1 is interpreted. When this is not set, EVAL is implemented
- ;; as a little bit of hackery wrapped around a call to COMPILE, i.e.
- ;; the system becomes a "compiler-only implementation" of Common Lisp.
- ;; As of sbcl-0.6.7, the compiler-only implementation is prototype code,
- ;; and much less mature than the old IR1 interpreter. Thus, the safe
- ;; thing is to leave :SB-INTERPRETER set. However, the compiler-only
- ;; system is noticeably smaller, so you might want to omit
- ;; :SB-INTERPRETER if you have a small machine.
- ;;
- ;; Probably, the compiler-only implementation will become more
- ;; stable someday, and support for the IR1 interpreter will then be
- ;; dropped. This will make the system smaller and easier to maintain
- ;; not only because we no longer need to support the interpreter,
- ;; but because code elsewhere in the system (the dumper, the debugger,
- ;; etc.) no longer needs special cases for interpreted code.
- :sb-interpreter
-
  ;; Do regression and other tests when building the system. You
  ;; might or might not want this if you're not a developer,
  ;; depending on how paranoid you are. You probably do want it if
  ;; you are a developer.
  :sb-test
 
- ;; :SB-PROPAGATE-FLOAT-TYPE and :SB-PROPAGATE-FUN-TYPE enable
- ;; some numeric optimizer code in the target compiler. They 
- ;; correspond to the :PROPAGATE-FLOAT-TYPE and :PROPAGATE-FUN-TYPE
- ;; features in the original CMU CL code, and while documentation 
- ;; existed for those, it seemed a little inconsistent. Despite the
- ;; name, :SB-PROPAGATE-FLOAT-TYPE seems to control not only
- ;; floating point optimizations, but some integer optimizations as
- ;; well.
- ;; 
- ;; CROSS-FLOAT-INFINITY-KLUDGE:
- ;;   * Even when these target features are enabled, the optimizations 
- ;;     aren't enabled in the cross-compiler, because some of them
- ;;     depend on floating point infinities, which aren't in general
- ;;     supported on the cross-compilation host.
- ;;   * This is supported by hacking the features out of the 
- ;;     *SHEBANG-FEATURES* list while we're building the cross-compiler.
- ;;     This is ugly and confusing and weird, but all the alternatives
- ;;     that I could think of seem messy and error-prone. That doesn't
- ;;     mean there's not a better way, though. Suggestions are welcome;
- ;;     or if you'd like to submit patches to make this code work
- ;;     without requiring floating point infinities, so that the entire
- ;;     problem goes away, that might be even better! -- WHN 2001-03-22
- :sb-propagate-float-type
- :sb-propagate-fun-type
-
- ;; Setting this makes more debugging information available.
- ;; If you aren't hacking or troubleshooting SBCL itself, you
- ;; probably don't want this set.
+ ;; Make more debugging information available (for debugging SBCL
+ ;; itself). If you aren't hacking or troubleshooting SBCL itself,
+ ;; you probably don't want this set.
  ;;
  ;; At least two varieties of debugging information are enabled by this
  ;; option:
@@ -139,6 +95,11 @@
  ;; readtable configured so that the system sources can be read.
  ; :sb-show
 
+ ;; Build SBCL with the old CMU CL low level debugger, "ldb". If 
+ ;; are aren't messing with CMU CL at a very low level (e.g. 
+ ;; trying to diagnose GC problems) you shouldn't need this.
+ ; :sb-ldb
+
  ;; This isn't really a target Lisp feature at all, but controls
  ;; whether the build process produces an after-xc.core file. This
  ;; can be useful for shortening the edit/compile/debug cycle if