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 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) (limited to 'manual/pthread_barrier_init.html') 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

-- cgit v1.2.3