X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=50b732ebd47abacce9b535583d0776613f90e113;hb=f2db6743b1fadeea9e72cb583d857851c87efcd4;hp=d614afa77adb5168860077ecb63ec5dd689631e9;hpb=bfb19d306581ac86feb4371846c4b9953d692dd8;p=sbcl.git diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr index d614afa..50b732e 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 @@ -296,8 +353,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 @@ -327,6 +383,9 @@ ;; 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 @@ -337,10 +396,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.) )