;;
; :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
;; 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
;; 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
;; 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.
;; 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
;; :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
projects / sbcl.git / blobdiff