X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=78139e0ca9c8365e2174e8242e056109cd4a6263;hb=f318d0b1654042ed8f1b887852a9ba1f539208e4;hp=3523114091bf9bbb2555cd85b308a88b45c3a06c;hpb=31f072311935e32751508ecf824905c6b58a1d95;p=sbcl.git diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr index 3523114..78139e0 100644 --- a/base-target-features.lisp-expr +++ b/base-target-features.lisp-expr @@ -7,10 +7,13 @@ ;;;; ;;;; Note that the recommended way to customize the features of a ;;;; local build of SBCL is not to edit this file, but instead to -;;;; tweak customize-target-features.lisp. If you define a function -;;;; in customize-target-features.lisp, it will be used to transform -;;;; the target features list after it's read and before it's used. -;;;; E.g. you can use code like this: +;;;; tweak customize-target-features.lisp. (You must create this file +;;;; first; it is not in the SBCL distribution, and is in fact +;;;; explicitly excluded from the distribution in places like +;;;; .cvsignore.) If you define a function in +;;;; customize-target-features.lisp, it will be used to transform the +;;;; target features list after it's read and before it's used. E.g., +;;;; you can use code like this: ;;;; (lambda (list) ;;;; (flet ((enable (x) (pushnew x list)) ;;;; (disable (x) (setf list (remove x list)))) @@ -54,14 +57,6 @@ ;; local-target-features.lisp-expr via make-config.sh, as alpha, ;; sparc and ppc ports don't currently support it. -- CSR, 2002-02-21 - ;; We're running under a UNIX. This is sort of redundant, and it was also - ;; sort of redundant under CMU CL, which we inherited it from: neither SBCL - ;; nor CMU CL supports anything but UNIX (and "technically not UNIX"es - ;; such as *BSD and Linux). But someday, maybe we might, and in that case - ;; we'd presumably remove this, so its presence conveys the information - ;; that the system isn't one which follows such a change. - :unix - ;; ;; features present in this particular build ;; @@ -107,11 +102,13 @@ ;; 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 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 + ;; Build SBCL with the old CMU CL low level debugger, "ldb". In the + ;; ideal world you would not need this unless you are 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). However, + ;; experience shows that sooner or later everyone lose()'s, in which + ;; case SB-LDB can at least provide an informative backtrace. + :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 @@ -141,6 +138,13 @@ ;; anyone who wants to collect such statistics in the future. ; :sb-dyncount + ;; Enable code for detecting concurrent accesses to the same hash-table + ;; in multiple threads. Note that this implementation is currently + ;; (2007-09-11) somewhat too eager: even though in the current implementation + ;; multiple readers are thread safe as long as there are no writers, this + ;; code will also trap multiple readers. + ; :sb-hash-table-debug + ;; Peter Van Eynde's increase-bulletproofness code for CMU CL ;; ;; Some of the code which was #+high-security before the fork has now @@ -162,6 +166,22 @@ ;; so caveat executor. ; :sb-thread + ;; lutex support + ;; + ;; While on linux we are able to use futexes for our locking + ;; primitive, on other platforms we don't have this luxury. NJF's + ;; lutexes present a locking API similar to the futex-based API that + ;; allows for sb-thread support on x86 OS X, Solaris and + ;; FreeBSD. + ;; + ; :sb-lutex + + ;; On some operating systems the FS segment register (used for SBCL's + ;; thread local storage) is not reliably preserved in signal + ;; handlers, so we need to restore its value from the pthread thread + ;; local storage. + ; :restore-tls-segment-register-from-tls + ;; 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 @@ -173,6 +193,11 @@ ;; character set. :sb-unicode + ;; Support for a full evaluator that can execute all the CL special + ;; forms, as opposed to the traditional SBCL evaluator which called + ;; COMPILE for everything complicated. + :sb-eval + ;; Record source location information for variables, classes, conditions, ;; packages, etc. Gives much better information on M-. in Slime, but ;; increases core size by about 100kB. @@ -208,6 +233,16 @@ ;; again, if anyone's sufficiently motivated. ; :long-float + ;; Some platforms don't use a 32-bit off_t by default, and thus can't + ;; handle files larger than 2GB. This feature will control whether + ;; we'll try to use platform-specific compilation options to enable a + ;; 64-bit off_t. The intent is for this feature to be automatically + ;; enabled by make-config.sh on platforms where it's needed and known + ;; to work, you shouldn't be enabling it manually. You might however + ;; want to disable it, if you need to pass file descriptors to + ;; foreign code that uses a 32-bit off_t. + ; :largefile + ;; ;; miscellaneous notes on other things which could have special significance ;; in the *FEATURES* list @@ -260,8 +295,7 @@ ;; :hppa ;; any PA-RISC CPU ;; :mips - ;; any MIPS CPU (in little-endian mode with :little-endian -- currently - ;; untested) + ;; any MIPS CPU (in little-endian mode with :little-endian) ;; ;; (CMU CL also had a :pentium feature, which affected the definition ;; of some floating point vops. It was present but not enabled or @@ -284,7 +318,16 @@ ;; :stack-allocatable-closures ;; The compiler can allocate dynamic-extent closures on stack. ;; + ;; :alien-callbacks + ;; Alien callbacks have been implemented for this platform. + ;; + ;; :compare-and-swap-vops + ;; The backend implements compare-and-swap VOPs. + ;; ;; operating system features: + ;; :unix = We're intended to run under some Unix-like OS. (This is not + ;; exclusive with the features which indicate which particular + ;; Unix-like OS we're intended to run under.) ;; :linux = We're intended to run under some version of Linux. ;; :bsd = We're intended to run under some version of BSD Unix. (This ;; is not exclusive with the features which indicate which @@ -297,8 +340,8 @@ ;; with the SunOS kernel. ;; :osf1 = We're intended to run under Tru64 (aka Digital Unix ;; aka OSF/1). - ;; (No others are supported by SBCL as of 0.9.6, but :hpux or :irix + ;; :win32 = We're intended to under some version of Microsoft Windows. + ;; (No others are supported by SBCL as of 1.0.8, but :hpux or :irix ;; support could be ported from CMU CL if anyone is sufficiently - ;; motivated to do so, and it'd even be possible, though harder, to - ;; port the system to Microsoft Windows.) + ;; motivated to do so.) )