X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=08f1a71004f185defc11e5a5c986374025f5e10b;hb=079ef9dad558ca07cb8178ef428bf738112174fa;hp=6d10856ecace0093a6402a48786b789b6ac6415f;hpb=98a76d4426660876dec6649b1e228d2e5b47f579;p=sbcl.git diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr index 6d10856..08f1a71 100644 --- a/base-target-features.lisp-expr +++ b/base-target-features.lisp-expr @@ -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 @@ -159,6 +159,26 @@ ;; Note that no consistent effort to audit the SBCL library code for ;; thread safety has been performed, so caveat executor. ; :sb-thread + + ;; Kernel support for futexes (so-called "fast userspace mutexes") is + ;; available in Linux 2.6 and some versions of 2.4 (Red Hat vendor + ;; kernels, possibly other vendors too). We can take advantage of + ;; these to do faster and probably more reliable mutex and condition + ;; variable support. An SBCL built with this feature will fall back + ;; to the old system if the futex() syscall is not available at + ;; runtime + ; :sb-futex + + ;; 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 @@ -252,7 +272,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 +281,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 +291,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