X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=doc%2Finternals-notes%2Fthreading-specials;h=56895e721fdc6ddd758adf3c6e989e5e55ae99e0;hb=3fa2feb10ab827fc6cc2a85287e78b6e66b7bf4d;hp=fd71da7e53837c867c842af81dd3f988af6f9ef2;hpb=3b96e3dcd35802e14cd86dc193debcc53a223c03;p=sbcl.git

diff --git a/doc/internals-notes/threading-specials b/doc/internals-notes/threading-specials
index fd71da7..56895e7 100644
--- a/doc/internals-notes/threading-specials
+++ b/doc/internals-notes/threading-specials
@@ -15,13 +15,12 @@ The goals are
 
 	When looking at a particular symbol, please annotate it in
 	this file when you figure out what it's for and how it's
-	changed.  To give us some confidence that we have reasonable
-	coverage, please don't just delete it if it looks ok.  Symbols
+	changed. To give us some confidence that we have reasonable
+	coverage, please don't just delete it if it looks ok. Symbols
 	shoud only be deleted here if they're obviously not specials
 	at all (e.g. functions with * in their names), or if the same
-	commit actually rids SBCL of the symbol itself (as we may soon
-	do for e.g. SB-SYS:*TASK-SELF*).  Otherwise, just add a
-	comment saying "read-only" or "unused" or whatever.
+	commit actually rids SBCL of the symbol itself. Otherwise,
+	just add a comment saying "read-only" or "unused" or whatever.
 
 	(3) anything else that comes to mind as potential trouble
         spots.  Global state in closures, etc etc
@@ -98,16 +97,11 @@ SB-LOOP::*LOOP-BIND-STACK*
 
 = PCL
 
-The PCL authors thought a bit about thread safety, adding
-(without-interrupts ...) in some places to protect critical forms.
-We've implemented their without-interrupts macro as an acquitision of
-*pcl-lock*, so we hope they've done it properly.
+Critical parts of PCL are protected by *world-lock* (particularly
+those dealing with class graph changes), and some with finer-grained locks.
 
-Largish parts of PCL should also be protected by the compiler lock,
-but sometimes it can be hard to tell...
-
-The most suspicious parts should probably be tested by asserting
-at various sites that the *PCL-LOCK* is held.
+accesses locked with a nice granularity
+   SB-PCL::*CLASSOID-CELLS*
 
 read-only & safe:
    SB-PCL::*BUILT-IN-TYPEP-COST* 
@@ -188,7 +182,6 @@ SB-PCL::*EMIT-FUNCTION-P*
 SB-PCL::*ENABLE-DFUN-CONSTRUCTOR-CACHING* 
 SB-PCL::*ENABLE-EMF-CALL-TRACING-P* 
 SB-PCL::*EQL-SPECIALIZER-TABLE* 
-SB-PCL::*FIND-CLASS* 
 SB-PCL::*GLOBAL-EFFECTIVE-METHOD-GENSYMS* 
 SB-PCL::*IN-GF-ARG-INFO-P* 
 SB-PCL::*IN-PRECOMPUTE-EFFECTIVE-METHODS-P* 
@@ -909,15 +902,6 @@ SB-KERNEL::*BUILT-IN-CLASSES*
 
 = dead stuff
 
-SB-SYS:*TASK-NOTIFY*    ; unused
-SB-SYS:*TASK-SELF*      ; unused
-SB-SYS:*TASK-DATA*      ; unused
-SB-SYS:*TYPESCRIPTPORT* ' unused
-SB-THREAD::*FOREGROUND-THREAD-STACK*    ; unused, I think
-
-
-
-
 ------------------------------------------------------------------------
 
 = unclassified