See ChangeLogs: preparing for new release.

3 files changed, 6 insertions, 15 deletions

diff --git a/manual/pthread_barrier_init.html b/manual/pthread_barrier_init.html
index 065c129..f581358 100644
--- a/manual/pthread_barrier_init.html
+++ b/manual/pthread_barrier_init.html
@@ -32,8 +32,7 @@ barrier referenced by <I>barrier</I> and release any resources used
 by the barrier. The effect of subsequent use of the barrier is
 undefined until the barrier is reinitialized by another call to
 <B>pthread_barrier_init</B> . An implementation may use this function
-to set <I>barrier</I> to an invalid value. The results are undefined
-if <B>pthread_barrier_destroy</B> is called when any thread is
+to set <I>barrier</I> to an invalid value. An error code is returned if <B>pthread_barrier_destroy</B> is called when any thread is
 blocked on the barrier, or if this function is called with an
 uninitialized barrier. 
 </P>
@@ -139,10 +138,8 @@ that these routines are implemented and may be used.</P>
 <DL>
 	<DD STYLE="margin-left: 0cm; margin-bottom: 0.5cm">In
 	<B><SPAN LANG="en-GB"><SPAN LANG="en-GB">pthreads-win32</SPAN></SPAN></B>,
-	<A HREF="pthread_barrier_wait.html"></A><A HREF="pthread_barrier_wait.html"><B>pthread_barrier_wait</B>(3)</A><A HREF="pthread_barrier_wait.html"></A>
-	may deadlock if the number of running threads able to wait on the
-	barrier object exceeds the value given as the <I><SPAN LANG="en-GB"><SPAN LANG="en-GB">count</SPAN></SPAN></I>
-	parameter in <B>pthread_barrier_init</B>. 
+	the behaviour of threads which enter <A HREF="pthread_barrier_wait.html"><B>pthread_barrier_wait</B>(3)</A>
+	while the barrier is being destroyed is undefined. 
 	</DD></DL>
 <H2>
 <A HREF="#toc9" NAME="sect9">See Also</A></H2>
diff --git a/manual/pthread_barrier_wait.html b/manual/pthread_barrier_wait.html
index 693d8bd..f407aa5 100644
--- a/manual/pthread_barrier_wait.html
+++ b/manual/pthread_barrier_wait.html
@@ -103,13 +103,7 @@ that this routine is implemented and may be used.</P>
 </P>
 <H2><A HREF="#toc11" NAME="sect11">Known Bugs</A></H2>
 <DL>
-	<DD STYLE="margin-left: 0cm; margin-bottom: 0.5cm">In
-	<B><SPAN LANG="en-GB">pthreads-win32</SPAN></B>,
-	<B>pthread_barrier_wait</B> may deadlock if the number of running
-	threads able to wait on the barrier object exceeds the value given
-	as the <I><SPAN LANG="en-GB">count</SPAN></I> parameter in
-	<A HREF="pthread_barrier_init.html"><B>pthread_barrier_init(3)</B></A>.
-		</DD></DL>
+	None.</DL>
 <H2>
 <A HREF="#toc9" NAME="sect9">See Also</A></H2>
 <P><A HREF="pthread_barrier_init.html"><B>pthread_barrier_destroy</B>(3)</A>,
diff --git a/manual/pthread_win32_attach_detach_np.html b/manual/pthread_win32_attach_detach_np.html
index 57f0339..f8cfc36 100644
--- a/manual/pthread_win32_attach_detach_np.html
+++ b/manual/pthread_win32_attach_detach_np.html
@@ -27,9 +27,9 @@ statically linking the library.</P>
 <P><B>BOOL pthread_win32_thread_attach_np (void);</B></P>
 <P><B>BOOL pthread_win32_thread_detach_np (void);</B></P>
 <H2><A HREF="#toc2" NAME="sect2">Description</A></H2>
-<P>These functions contain the code normally run via <B>dllMain</B>
+<P>These functions contain the code normally run via <b>dllMain</b>
 when the library is used as a dll but which need to be called
-explicitly by an application when the library is statically linked.</P>
+explicitly by an application when the library is statically linked. As of version 2.9.0,  the  static library built using either MSC or GCC includes RT hooks which will call the pthread_win32_process_*_np routines automatically on  start/exit of the application.</P>
 <P>You will need to call <B>pthread_win32_process_attach_np</B>
 before you can call any pthread routines when statically linking. You
 should call <B>pthread_win32_process_detach_np</B> before exiting