From a3ea0b24409b89bd08c0a2268dbae834724734df Mon Sep 17 00:00:00 2001 From: rpj Date: Sun, 20 Jun 2010 03:31:18 +0000 Subject: See ChangeLogs: preparing for new release. --- manual/pthread_barrier_init.html | 9 +++------ manual/pthread_barrier_wait.html | 8 +------- manual/pthread_win32_attach_detach_np.html | 4 ++-- 3 files changed, 6 insertions(+), 15 deletions(-) (limited to 'manual') 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 barrier 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 pthread_barrier_init . An implementation may use this function -to set barrier to an invalid value. The results are undefined -if pthread_barrier_destroy is called when any thread is +to set barrier to an invalid value. An error code is returned if pthread_barrier_destroy is called when any thread is blocked on the barrier, or if this function is called with an uninitialized barrier.

@@ -139,10 +138,8 @@ that these routines are implemented and may be used.

In pthreads-win32, - pthread_barrier_wait(3) - may deadlock if the number of running threads able to wait on the - barrier object exceeds the value given as the count - parameter in pthread_barrier_init. + the behaviour of threads which enter pthread_barrier_wait(3) + while the barrier is being destroyed is undefined.

See Also

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.

Known Bugs

-
In - pthreads-win32, - pthread_barrier_wait may deadlock if the number of running - threads able to wait on the barrier object exceeds the value given - as the count parameter in - pthread_barrier_init(3). -
+ None.

See Also

pthread_barrier_destroy(3), 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.

BOOL pthread_win32_thread_attach_np (void);

BOOL pthread_win32_thread_detach_np (void);

Description

-

These functions contain the code normally run via dllMain +

These functions contain the code normally run via dllMain when the library is used as a dll but which need to be called -explicitly by an application when the library is statically linked.

+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.

You will need to call pthread_win32_process_attach_np before you can call any pthread routines when statically linking. You should call pthread_win32_process_detach_np before exiting -- cgit v1.2.3