;; the executable I'm running.
:sb-doc
- ;; Do regression and other tests when building the system. You
- ;; might or might not want this if you're not a developer,
- ;; depending on how paranoid you are. You probably do want it if
- ;; you are a developer.
+ ;; Do regression and other tests when building the system. You might
+ ;; or might not want this if you're not a developer, depending on how
+ ;; paranoid you are. You probably do want it if you are a developer.
+ ;; This test does not affect the target system (in much the same way
+ ;; as :sb-after-xc-core, below).
:sb-test
;; Make more debugging information available (for debugging SBCL
; :high-security
; :high-security-support
- ;; multiprocessing support
+ ;; low-level thread primitives support
;;
- ;; This is not maintained or tested in current SBCL. I haven't gone out
- ;; of my way to break it, but since it's derived from an old version of
- ;; CMU CL where multiprocessing was pretty shaky, it's likely to be very
- ;; flaky now.
- ;; :MP enables multiprocessing
- ;; :MP-I486 is used, only within the multiprocessing code, to control
- ;; what seems to control processor-version-specific code. It's
- ;; probably for 486 or later, i.e. could be set as long as
- ;; you know you're not running on a 386, but it doesn't seem
- ;; to be documented anywhere, so that's just a guess.
- ; :mp
- ; :mp-i486
-
+ ;; As of SBCL 0.8, this is only supposed to work in x86 Linux, on which
+ ;; system it's 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
+ ; :sb-thread
+
;; 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.
;; any Intel 386 or better, or compatibles like the AMD K6 or K7
;; :alpha
;; DEC/Compaq Alpha CPU
- ;; (No other CPUs are supported by SBCL as of 0.6.12.15, but SPARC or
- ;; PowerPC support could be ported from CMU CL if anyone is
- ;; sufficiently motivated to do so, or if you're *really* motivated,
- ;; you could write a port from scratch for a new CPU architecture.)
+ ;; :sparc
+ ;; any Sun UltraSPARC (possibly also non-Ultras -- currently untested)
+ ;; :ppc
+ ;; any PowerPC CPU
+ ;; :hppa
+ ;; any PA-RISC CPU
+ ;; :mips
+ ;; any MIPS CPU (in little-endian mode with :little-endian -- currently
+ ;; untested)
+ ;;
;; (CMU CL also had a :pentium feature, which affected the definition
- ;; of some floating point vops. It was present but not enabled or
- ;; documented in the CMU CL code that SBCL is derived from, and is
- ;; present but stale in SBCL as of 0.6.12.)
+ ;; of some floating point vops. It was present but not enabled or
+ ;; documented in the CMU CL code that SBCL is derived from, and has
+ ;; now been moved to the backend-subfeatures mechanism.)
;;
;; properties derived from the machine architecture
;; :control-stack-grows-downward-not-upward
;; is not exclusive with the features which indicate which
;; particular version of BSD we're intended to run under.)
;; :freebsd = We're intended to run under FreeBSD.
- ;; :openbsd = We're intended to run under FreeBSD.
- ;; (No others are supported by SBCL as of 0.6.7, but :hpux or
- ;; :solaris 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.)
+ ;; :openbsd = We're intended to run under OpenBSD.
+ ;; :sunos = We're intended to run under Solaris user environment
+ ;; with the SunOS kernel.
+ ;; :osf1 = We're intended to run under Tru64 (aka Digital Unix
+ ;; aka OSF/1).
+ ;; (No others are supported by SBCL as of 0.7.5, 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 or MacOS X.)
)
projects / sbcl.git / blobdiff