X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=8237b15ef5a6c906dfe6bdb0230d544f327f3427;hb=597826f00530e8d0c6f4a8ccda2e366f56b65579;hp=c6a5479d52daea11b3545f1af835b6374b2549db;hpb=bcc4957521680d80cb295645deda94697e972ce7;p=sbcl.git diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr index c6a5479..8237b15 100644 --- a/base-target-features.lisp-expr +++ b/base-target-features.lisp-expr @@ -57,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 ;; @@ -146,6 +138,71 @@ ;; 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 + + ;; Enabled automatically by make-config.sh for platforms which implement + ;; the %READ-CYCLE-COUNTER VOP. Can be disabled manually: affects TIME. + ;; + ;; FIXME: Should this be :SB-CYCLE-COUNTER instead? If so, then the same goes + ;; for :COMPARE-AND-SWAP-VOPS as well, and a bunch of others. Perhaps + ;; built-time convenience features like this should all live in eg. SB!INT + ;; instead? + ;; + ; :cycle-counter + + ;; Enabled automatically for platforms which implement complex arithmetic + ;; VOPs. Such platforms should implement real-complex, complex-real and + ;; complex-complex addition and subtractions (for complex-single-float + ;; and complex-double-float). They should also also implement complex-real + ;; and real-complex multiplication, complex-real division, and + ;; sb!vm::swap-complex, which swaps the real and imaginary parts. + ;; Finally, they should implement conjugate and complex-real, real-complex + ;; and complex-complex CL:= (complex-complex EQL would usually be a good + ;; idea). + ;; + ; :complex-float-vops + + ;; Enabled automatically for platforms which implement VOPs for EQL + ;; of single and double floats. + ;; + ; :float-eql-vops + + ;; Enabled automatically for platform that can implement inline constants. + ;; + ;; Such platform must implement 5 functions, in SB!VM: + ;; * canonicalize-inline-constant: converts a constant descriptor (list) into + ;; a canonical description, to be used as a key in an EQUAL hash table + ;; and to guide the generation of the constant itself. + ;; * inline-constant-value: given a canonical constant descriptor, computes + ;; two values: + ;; 1. A label that will be used to emit the constant (usually a + ;; sb!assem:label) + ;; 2. A value that will be returned to code generators referring to + ;; the constant (on x86oids, an EA object) + ;; * sort-inline-constants: Receives a vector of unique constants; + ;; the car of each entry is the constant descriptor, and the cdr the + ;; corresponding label. Destructively returns a vector of constants + ;; sorted in emission order. It could actually perform arbitrary + ;; modifications to the vector, e.g. to fuse constants of different + ;; size. + ;; * emit-constant-segment-header: receives the vector of sorted constants + ;; and a flag (true iff speed > space). Expected to emit padding + ;; of some sort between the ELSEWHERE segment and the constants, or some + ;; metadata. + ;; * emit-inline-constant: receives a constant descriptor and its associated + ;; label. Emits the constant. + ;; + ;; Implementing this features lets VOP generators use sb!c:register-inline-constant + ;; to get handles (as returned by sb!vm:inline-constant-value) from constant + ;; descriptors. + ;; + ; :inline-constants + ;; Peter Van Eynde's increase-bulletproofness code for CMU CL ;; ;; Some of the code which was #+high-security before the fork has now @@ -159,23 +216,17 @@ ;; low-level thread primitives support ;; - ;; 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. + ;; As of SBCL 1.0.33.26, threads are part of the default build on + ;; x86oid Linux. Other platforms that support them include + ;; x86oid Darwin, FreeBSD, and Solaris. ; :sb-thread - ;; lutex support + ;; futex 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. + ;; primitive, on other platforms we don't have this luxury. ;; - ; :sb-lutex + ; :sb-futex ;; On some operating systems the FS segment register (used for SBCL's ;; thread local storage) is not reliably preserved in signal @@ -183,6 +234,11 @@ ;; local storage. ; :restore-tls-segment-register-from-tls + ;; On some x86oid operating systems (darwin) SIGTRAP is not reliably + ;; delivered for the INT3 instruction, so we use the UD2 instruction + ;; which generates SIGILL instead. + ; :ud2-breakpoints + ;; 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 @@ -194,11 +250,22 @@ ;; 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. :sb-source-locations + ;; Record xref data for SBCL internals. This can be rather useful for + ;; people who want to develop on SBCL itself because it'll make M-? + ;; (slime-edit-uses) work which lists call/expansion/etc. sites. + ;; It'll increase the core size by major 5-6mB, though. + ; :sb-xref-for-internals + ;; 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. @@ -229,6 +296,27 @@ ;; 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 + + ;; Enabled automatically on platforms that have VOPs to compute the + ;; high half of a full word-by-word multiplication. When disabled, + ;; SB-KERNEL:%MULTIPLY-HIGH is implemented in terms of + ;; SB-BIGNUM:%MULTIPLY. + ; :multiply-high-vops + + ;; SBCL has optional support for zlib-based compressed core files. Enable + ;; this feature to compile it in. Obviously, doing so adds a dependency + ;; on zlib. + ; :sb-core-compression + ;; ;; miscellaneous notes on other things which could have special significance ;; in the *FEATURES* list @@ -281,8 +369,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 @@ -308,7 +395,17 @@ ;; :alien-callbacks ;; Alien callbacks have been implemented for this platform. ;; + ;; :compare-and-swap-vops + ;; The backend implements compare-and-swap VOPs. + ;; + ;; :memory-barrier-vops + ;; Memory barriers (for multi-threaded synchronization) have been + ;; implemented for this platform. + ;; ;; 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 @@ -319,10 +416,11 @@ ;; :darwin = We're intended to run under Darwin (including MacOS X). ;; :sunos = We're intended to run under Solaris user environment ;; with the SunOS kernel. + ;; :hpux = We're intended to run under HP-UX 11.11 or later ;; :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.) )