diff options
| author | rpj <rpj> | 2005-01-25 05:38:44 +0000 | 
|---|---|---|
| committer | rpj <rpj> | 2005-01-25 05:38:44 +0000 | 
| commit | 2c2624655dfa830dafef17e87b739f876f098f8c (patch) | |
| tree | 3ddbbf98d7ccd7d31badab2cc78ed2de7161046b | |
| parent | e1d015c3dc92a70d787a5686bc7518c6f42fe81f (diff) | |
''
| -rw-r--r-- | ANNOUNCE | 6 | ||||
| -rw-r--r-- | CONTRIBUTORS | 1 | ||||
| -rw-r--r-- | ChangeLog | 7 | ||||
| -rw-r--r-- | NEWS | 13 | 
4 files changed, 25 insertions, 2 deletions
| @@ -1,10 +1,14 @@ -		 PTHREADS-WIN32 SNAPSHOT 2005-01-03
 +		 PTHREADS-WIN32 SNAPSHOT 2005-01-25
  		 ----------------------------------
  	 Web Site: http://sources.redhat.com/pthreads-win32/
  	FTP Site: ftp://sources.redhat.com/pub/pthreads-win32
  	 Maintainer: Ross Johnson <rpj@callisto.canberra.edu.au>
 +[Please note: snapshots from 2004-11-03 are using a new mutex implementation +and should be regarded as beta code. You may not want to use it in production +yet but please try it if you can.] +  We are pleased to announce the availability of a new snapshot of
  Pthreads-win32, an Open Source Software implementation of the
  Threads component of the POSIX 1003.1 2001 Standard for Microsoft's
 diff --git a/CONTRIBUTORS b/CONTRIBUTORS index 115e9dd..c23ce98 100644 --- a/CONTRIBUTORS +++ b/CONTRIBUTORS @@ -74,6 +74,7 @@ Alexander Terekhov	TEREKHOV at de dot ibm dot com  					condition variables;  					enhancements to semaphores;  					enhancements to mutexes; +					new mutex implementation in 'futex' style;  					system clock change handling re CV timeouts;  					bug fixes.  Thomas Pfaff		tpfaff at gmx dot net @@ -1,10 +1,15 @@ +2005-01-25  Ralf Kubis  <RKubis at mc.com>
 + +	* Attempted acquisition of recursive mutex was causing waiting +	threads to not be woken when the mutex is released. +  2005-01-01  Konstantin Voronkov  <beowinkle at yahoo.com>
  	* pthread_mutex_lock.c (pthread_mutex_lock): The new atomic exchange
  	mutex algorithm is known to allow a thread to steal the lock off
  	FIFO waiting threads. The next waiting FIFO thread gets a spurious
  	wake-up and must attempt to re-acquire the lock. The woken thread
 -	was setting itself as the the mutex's owner before the re-acquisition.
 +	was setting itself as the mutex's owner before the re-acquisition.
  2004-11-22  Ross Johnson  <rpj at callisto.canberra.edu.au>
 @@ -1,3 +1,16 @@ +SNAPSHOT 2005-01-25
 +-------------------
 +
 +Bug fixes
 +---------
 +
 +* Attempted acquisition of a recursive mutex could cause waiting threads
 +to not be woken when the mutex was released.
 +- Ralf Kubis  <RKubis at mc.com>
 +
 +* Various package omissions have been fixed. +
 +
  SNAPSHOT 2005-01-03
  -------------------
 | 
