Cleanup and fixes to thread priority management. Other minor changes.snap-2003-09-18

1 files changed, 30 insertions, 10 deletions

diff --git a/NEWS b/NEWS
index 04d8483..008f8f2 100644
--- a/NEWS
+++ b/NEWS
@@ -1,15 +1,35 @@
-SNAPSHOT 2003-09-04

+SNAPSHOT 2003-09-18

 -------------------

 

+Cleanup of thread priority management. In particular, setting of thread
+priority now attempts to map invalid Win32 values within the range returned
+by sched_get_priority_min/max() to useful values. See README.NONPORTABLE
+under "Thread priority".
+
 Bug fixes

 ---------
-* ptw32_cancelableWait() now allows cancelation of waiting implicit POSIX
-threads.
+* pthread_getschedparam() now returns the priority given by the most recent
+call to pthread_setschedparam() or established by pthread_create(), as
+required by the standard. Previously, pthread_getschedparam() incorrectly
+returned the running thread priority at the time of the call, which may have
+been adjusted or temporarily promoted/demoted.
+
+* sched_get_priority_min() and sched_get_priority_max() now return -1 on error
+and set errno. Previously, they incorrectly returned the error value directly.
+
+
+SNAPSHOT 2003-09-04

+-------------------

+

+Bug fixes

+---------

+* ptw32_cancelableWait() now allows cancelation of waiting implicit POSIX

+threads.

 
-New test
---------
-* cancel8.c tests cancelation of Win32 threads waiting at a POSIX cancelation
-point.
+New test

+--------

+* cancel8.c tests cancelation of Win32 threads waiting at a POSIX cancelation

+point.

 
 
 SNAPSHOT 2003-09-03

@@ -53,9 +73,9 @@ needs a pthread_t as a parameter of course). A Win32 thread can discover it's ow
 POSIX thread ID by calling pthread_self(), which will create the handle if

 necessary and return the pthread_t value.

 
-New tests
----------
-Test the above new feature.
+New tests

+---------

+Test the above new feature.

 
 
 SNAPSHOT 2003-08-19