X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=74bf08306c5f57a9cab99b141acf3920370d2008;hb=bcd323c39d6f5f80020ba4a5d9eb8d348c6cc499;hp=8237b15ef5a6c906dfe6bdb0230d544f327f3427;hpb=d6f9676ae94419cb5544c45821a8d31adbc1fbe8;p=sbcl.git diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr index 8237b15..74bf083 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 @@ -232,7 +238,7 @@ ;; 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 + ; :restore-fs-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 @@ -266,6 +272,11 @@ ;; It'll increase the core size by major 5-6mB, though. ; :sb-xref-for-internals + ;; We support package local nicknames. No :sb-prefix here as we vainly + ;; believe our API is worth copying to other implementations as well. + ;; This doesn't affect the build at all, merely declares how things are. + :package-local-nicknames + ;; 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. @@ -317,6 +328,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