Remove references to missing linux_threads.c from documentation

* README.md (copyright): Change linux_threads.c to pthread_stop_world.c
and pthread_support.c files.
* doc/README.DGUX386: Remove reference to linux-threads.c file.
* doc/README.environment (GC_RETRY_SIGNALS, GC_NO_RETRY_SIGNALS):
Likewise.
* doc/gcdescr.html: Likewise.
* doc/README.DGUX386: Update information how to pass DEBUG_THREADS to
make.
* doc/gcdescr.html: Update threads support information for Irix and
Solaris.
* include/private/gc_locks.h: Remove reference to linux-threads.c in
a comment.
* pthread_support.c: Likewise.

3 files changed, 4 insertions, 17 deletions

diff --git a/doc/README.DGUX386 b/doc/README.DGUX386
index 0aa89bdf..48c800b8 100644
--- a/doc/README.DGUX386
+++ b/doc/README.DGUX386
@@ -24,13 +24,7 @@
 
      To enable debugging messages please do:
      1) Add the "--enable-gc-debug" flag during configuration.
-     2) Edit the file linux-threads.c and uncomment the line:
-
-     /* #define DEBUG_THREADS 1 */ to --->
-
-     #define DEBUG_THREADS 1
-
-     Then give "make" as usual.
+     2) Pass "CFLAGS=-DDEBUG_THREADS" to "make".
 
      In a machine with 4 CPUs (my own machine) the option parallel
      mark (aka --enable-parallel-mark) makes a BIG difference.
diff --git a/doc/README.environment b/doc/README.environment
index 7c7096c5..7d4d96c4 100644
--- a/doc/README.environment
+++ b/doc/README.environment
@@ -97,7 +97,7 @@ GC_PRINT_BACK_HEIGHT - Print max length of chain through unreachable objects
                      (http://www.hpl.hp.com/techreports/2001/HPL-2001-251.html).
 
 GC_RETRY_SIGNALS, GC_NO_RETRY_SIGNALS - Try to compensate for lost
-                     thread suspend signals in linux_threads.c.  On by
+                     thread suspend signals (Pthreads only).  On by
                      default for GC_OSF1_THREADS, off otherwise.  Note
                      that this does not work around a possible loss of
                      thread restart signals.  This seems to be necessary for
diff --git a/doc/gcdescr.html b/doc/gcdescr.html
index 07afd7cc..5b4b9fee 100644
--- a/doc/gcdescr.html
+++ b/doc/gcdescr.html
@@ -534,23 +534,16 @@ common Pthreads implementations.
 In particular, it is very difficult for the collector to stop all other
 threads in the system and examine the register contents.  This is currently
 accomplished with very different mechanisms for some Pthreads
-implementations.  The Solaris implementation temporarily disables much
-of the user-level threads implementation by stopping kernel-level threads
-("lwp"s).  The Linux/HPUX/OSF1 and Irix implementations sends signals to
+implementations.  For Linux/HPUX/OSF1, Solaris and Irix it sends signals to
 individual Pthreads and has them wait in the signal handler.
 <P>
 The Linux and Irix implementations use
 only documented Pthreads calls, but rely on extensions to their semantics.
-The Linux implementation <TT>linux_threads.c</tt> relies on only very
+The Linux implementation <TT>pthread_stop_world.c</tt> relies on only very
 mild extensions to the pthreads semantics, and already supports a large number
 of other Unix-like pthreads implementations.  Our goal is to make this the
 only pthread support in the collector.
 <P>
-(The Irix implementation is separate only for historical reasons and should
-clearly be merged.  The current Solaris implementation probably performs
-better in the uniprocessor case, but does not support thread operations in the
-collector.  Hence it cannot support the parallel marker.)
-<P>
 All implementations must
 intercept thread creation and a few other thread-specific calls to allow
 enumeration of threads and location of thread stacks.  This is current