PROBLEM: (80225, 81884, 82170, 82273,
          82309) (PATCH ID: OSF510-039)
********
This patch for Compaq POSIX Threads Library fixes the following problems:

1. A threaded applications may not recover the use of a CPU following an 
   offline/online procedure.

2. User threads blocked in the kernel against a specific VP may never unblock.

3. Problems with libpthread tracing for Totalview debugger 
   
4. User threads are not bound to the correct RAD upon returning from 
   pthread_rad_attach.


PROBLEM: (83270) (PATCH ID: OSF510-212)
********
The context switch code would only clear the floating point enable
bit when context switching away from a thread which was not
terminated. If the terminated thread had enabled the floating point
unit, the newly context-switched-to thread would be using its
floating point state instead of its saved state.


PROBLEM: (117-1-16330) (PATCH ID: OSF510-206)
********
    This problem occurs when using the user level context switching (ucontext)
    routines and switching a thread's stack. The result is that the pthread
    mutex API routines can return EINVAL because we were unable to validate
    the mutex.  This problem has been corrected by this patch.


PROBLEM: (83943) (PATCH ID: OSF510-109)
********
This patch fixes a bug in the POSIX Threads Library for Tru64 UNIX V5.1
that would result in a DECthreads Bugcheck and process termination.  
Threaded applications might encounter this problem when pthread_kill() 
is used on a thread that is marked as blocked in the kernel.   This
problem is identified by a stack trace similar to the following, where
the __errBugcheck frame occurs right after the _schReadyForInterrupt frame:
0 __nxm_thread_kill(0x3ff800e3834, 0x20002225038, 0x3ff805ce968, ...
1 __sigAbortProcess(0x20, 0x0, 0x0, 0x0, 0x20002227600) [0x3ff805b752c] ...
2 __errBugcheck(0x3ff805934b8, 0x3, 0x20002227600, 0x20001bf7cc2, ...
3 __schReadyForInterrupt(0x1e, 0x20002227600, 0x3ffc01b5050, 0x0, ...
4 pthread_kill(0x3ffbfdf43d8, 0x3ffbfdf4388, 0xe, 0x177db030, ...
...