X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=22530df0ebe11521a607a3e91205abdd629da397;hb=ad2b04d910cfc097712f19f05af9bb679ee17130;hp=019b37efcf557566e2bcaf737fa6d9bfdab31db8;hpb=7976926f8112b708d5927a69923cf7a3dd003c55;p=sbcl.git diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr index 019b37e..22530df 100644 --- a/base-target-features.lisp-expr +++ b/base-target-features.lisp-expr @@ -122,6 +122,12 @@ ;; original CMU CL code.) ; :sb-show-assem + ;; Compile the C runtime with support for low-level debugging output + ;; through FSHOW and FSHOW_SIGNAL. If enabled, this feature allows + ;; users to turn on such debugging output using environment variables at + ;; run-time. + ; :sb-qshow + ;; Setting this makes SBCL more "fluid", i.e. more amenable to ;; modification at runtime, by suppressing various INLINE declarations, ;; compiler macro definitions, FREEZE-TYPE declarations; and by @@ -221,15 +227,12 @@ ;; 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 @@ -320,6 +323,26 @@ ;; on zlib. ; :sb-core-compression + ;; On certain thread-enabled platforms, synchronization between threads + ;; for the purpose of stopping and starting the world around GC can be + ;; performed using safepoints instead of signals. Enable this feature + ;; to compile with safepoints and to use them for GC. + ;; (Replaces use of SIG_STOP_FOR_GC.) + ; :sb-safepoint + + ;; When compiling with safepoints, the INTERRUPT-THREAD mechanism can + ;; also use safepoints to roll the target thread to a point at which it + ;; can be interrupted safely, instead of using a signal for this + ;; purpose. Enable this feature in addition to :SB-SAFEPOINT to enable + ;; such behaviour. + ;; (Replaces use of SIGPIPE, except to wake up syscalls.) + ; :sb-thruption + + ;; When compiling with safepoints and thruptions, the TIMER facility + ;; can replace its use of setitimer with a background thread. + ;; (Replaces use of SIGALRM.) + ; :sb-wtimer + ;; ;; miscellaneous notes on other things which could have special significance ;; in the *FEATURES* list