X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=7bd7caff6a787a24a4164978c96b3c5a4d71d4e9;hb=883474646eb02d2fc0de5dcf4c63cf7ff794b2eb;hp=f3895074c55b00b868c56a6361eb9c9926c383d4;hpb=a157ed0be79751f85b8243c06102eea95af06aa3;p=sbcl.git

diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr
index f389507..7bd7caf 100644
--- a/base-target-features.lisp-expr
+++ b/base-target-features.lisp-expr
@@ -167,6 +167,42 @@
  ;;
  ; :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
@@ -180,12 +216,9 @@
 
  ;; 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
@@ -204,6 +237,11 @@
  ;; 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
@@ -225,6 +263,12 @@
  ;; 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.