X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=base-target-features.lisp-expr;h=f1110c4424a5fac278e1cb306676020b670eed30;hb=6b8baeece6cf870e3f979a9f09c32985c64c04de;hp=9b519a0ee9f72007d0da04f65a65f3521d8ebe07;hpb=b822fdd53a4dcfda0df39dcdfd73967921ddf5ad;p=sbcl.git

diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr
index 9b519a0..f1110c4 100644
--- a/base-target-features.lisp-expr
+++ b/base-target-features.lisp-expr
@@ -138,6 +138,23 @@
  ;; anyone who wants to collect such statistics in the future.
  ; :sb-dyncount
 
+ ;; Enable code for detecting concurrent accesses to the same hash-table
+ ;; in multiple threads. Note that this implementation is currently
+ ;; (2007-09-11) somewhat too eager: even though in the current implementation
+ ;; multiple readers are thread safe as long as there are no writers, this
+ ;; code will also trap multiple readers.
+ ; :sb-hash-table-debug
+
+ ;; Enabled automatically by make-config.sh for platforms which implement
+ ;; the %READ-CYCLE-COUNTER VOP. Can be disabled manually: affects TIME.
+ ;;
+ ;; FIXME: Should this be :SB-CYCLE-COUNTER instead? If so, then the same goes
+ ;; for :COMPARE-AND-SWAP-VOPS as well, and a bunch of others. Perhaps
+ ;; built-time convenience features like this should all live in eg. SB!INT
+ ;; instead?
+ ;;
+ ; :cycle-counter
+
  ;; Peter Van Eynde's increase-bulletproofness code for CMU CL
  ;;
  ;; Some of the code which was #+high-security before the fork has now
@@ -288,8 +305,7 @@
  ;;   :hppa
  ;;      any PA-RISC CPU
  ;;   :mips
- ;;      any MIPS CPU (in little-endian mode with :little-endian -- currently
- ;;      untested)
+ ;;      any MIPS CPU (in little-endian mode with :little-endian)
  ;;
  ;; (CMU CL also had a :pentium feature, which affected the definition
  ;; of some floating point vops. It was present but not enabled or