X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=e7b6406eeda8dcec720dacdbabaeb349fa89a18e;hb=4d9ce212ecdef5af8356873b56f88c72c4ed113d;hp=c6e3c90197ceeca26180a10ce38d772894b70139;hpb=be76f6319dcb41477209676e6f26e0030e4659ba;p=sbcl.git

diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr
index c6e3c90..e7b6406 100644
--- a/base-target-features.lisp-expr
+++ b/base-target-features.lisp-expr
@@ -13,7 +13,7 @@
 ;;;; E.g. you can use code like this:
 ;;;;    (lambda (list)
 ;;;;      (flet ((enable (x) (pushnew x list))
-;;;;    	 (disable (x) (setf list (remove x list))))
+;;;;             (disable (x) (setf list (remove x list))))
 ;;;;        #+nil (enable :sb-show)
 ;;;;        (enable :sb-after-xc-core)
 ;;;;        #+nil (disable :sb-doc)
@@ -107,10 +107,10 @@
  ;; 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, or trying to debug assembly
- ;; code for a port to a new CPU) you shouldn't need this.
+ ;; Build SBCL with the old CMU CL low level debugger, "ldb". If are
+ ;; aren't messing with SBCL at a very low level (e.g., trying to
+ ;; diagnose GC problems, or trying to debug assembly code for a port
+ ;; to a new CPU) you shouldn't need this.
  ; :sb-ldb
 
  ;; This isn't really a target Lisp feature at all, but controls
@@ -147,28 +147,37 @@
  ;; been either made unconditional, deleted, or rewritten into
  ;; unrecognizability, but some remains. What remains is not maintained
  ;; or tested in current SBCL, but I haven't gone out of my way to
- ;; break it, either. 
+ ;; break it, either.
  ;;
  ; :high-security
  ; :high-security-support
 
  ;; low-level thread primitives support
  ;;
- ;; As of SBCL 0.8,  this is only supposed to work in x86 Linux, on which
- ;; system it's implemented using clone(2) and the %fs segment register.
- ;; Note that no consistent effort to audit the SBCL library code for
- ;; thread safety has been performed, so caveat executor
+ ;; As of SBCL 0.8, this is only supposed to work in x86 Linux with
+ ;; NPTL support (usually kernel 2.6, though sme Red Hat distributions
+ ;; with older kernels also have it) and is implemented using clone(2)
+ ;; and the %fs segment register.  Note that no consistent effort to
+ ;; audit the SBCL library code for thread safety has been performed,
+ ;; so caveat executor.
  ; :sb-thread
- 
+
+ ;; Support for detection of unportable code (when applied to the
+ ;; COMMON-LISP package, or SBCL-internal pacakges) or bad-neighbourly
+ ;; code (when applied to user-level packages), relating to material
+ ;; alteration to packages or to bindings in symbols in packages.
+ :sb-package-locks
+
+ ;; Support for the entirety of the 21-bit character space defined by
+ ;; the Unicode consortium, rather than the classical 8-bit ISO-8859-1
+ ;; character set.
+ :sb-unicode
+
  ;; This affects the definition of a lot of things in bignum.lisp. It
  ;; doesn't seem to be documented anywhere what systems it might apply
  ;; to. It doesn't seem to be needed for X86 systems anyway.
  ; :32x16-divide
 
- ;; This is probably true for some processor types, but not X86. It
- ;; affects a lot of floating point code.
- ; :negative-zero-is-not-zero
-
  ;; This is set in classic CMU CL, and presumably there it means
  ;; that the floating point arithmetic implementation
  ;; conforms to IEEE's standard. Here it definitely means that the
@@ -199,6 +208,10 @@
  ;; in the *FEATURES* list
  ;;
 
+ ;; Any target feature which affects binary compatibility of fasl files
+ ;; needs to be recorded in *FEATURES-POTENTIALLY-AFFECTING-FASL-FORMAT*
+ ;; (elsewhere).
+
  ;; notes on the :NIL and :IGNORE features:
  ;;
  ;; #+NIL is used to comment out forms. Occasionally #+IGNORE is used
@@ -227,7 +240,7 @@
  ;; notes on local features (which are set automatically by the
  ;; configuration script, and should not be set here unless you
  ;; really, really know what you're doing):
- ;; 
+ ;;
  ;; machine architecture features:
  ;;   :x86
  ;;      any Intel 386 or better, or compatibles like the AMD K6 or K7
@@ -242,7 +255,7 @@
  ;;   :mips
  ;;      any MIPS CPU (in little-endian mode with :little-endian -- currently
  ;;      untested)
- ;;   
+ ;;
  ;; (CMU CL also had a :pentium feature, which affected the definition
  ;; of some floating point vops. It was present but not enabled or
  ;; documented in the CMU CL code that SBCL is derived from, and has
@@ -252,7 +265,7 @@
  ;;   :control-stack-grows-downward-not-upward
  ;;     On the X86, the Lisp control stack grows downward. On the
  ;;     other supported CPU architectures as of sbcl-0.7.1.40, the
- ;;     system stack grows upward. 
+ ;;     system stack grows upward.
  ;;   Note that there are other stack-related differences between the
  ;;   X86 port and the other ports. E.g. on the X86, the Lisp control
  ;;   stack coincides with the C stack, meaning that on the X86 there's
@@ -261,6 +274,9 @@
  ;;   just parameterized by #!+X86, but it'd probably be better to
  ;;   use new flags like :CONTROL-STACK-CONTAINS-C-STACK.
  ;;
+ ;;   :stack-allocatable-closures
+ ;;     The compiler can allocate dynamic-extent closures on stack.
+ ;;
  ;; operating system features:
  ;;   :linux   = We're intended to run under some version of Linux.
  ;;   :bsd     = We're intended to run under some version of BSD Unix. (This
@@ -268,6 +284,7 @@
  ;;              particular version of BSD we're intended to run under.)
  ;;   :freebsd = We're intended to run under FreeBSD.
  ;;   :openbsd = We're intended to run under OpenBSD.
+ ;;   :netbsd  = We're intended to run under NetBSD.
  ;;   :sunos   = We're intended to run under Solaris user environment
  ;;              with the SunOS kernel.
  ;;   :osf1    = We're intended to run under Tru64 (aka Digital Unix