Worked with GCC, but support blocks is disabled... :(
On 2/27/11 1:42 AM, Danilo Egea wrote:
Hi guys,
Anyone know what's going on?
PS: with clang-devel
libtool: compile: clang -DHAVE_CONFIG_H -I. -I../config -I.. -I..
-fPIC -MT time.lo -MD -MP -MF .deps/time.Tpo -c shims/time.c -fPIC
On FreeBSD-8.1 this page says:
The pthread_cond_signal() function unblocks one thread waiting for the
condition variable cond.
On Linux it says:
The /pthread_cond_signal/() function shall unblock at least one of the
threads that are blocked on the specified condition variable /cond/ (if
any
Forwarding to standards@ and davidxu@ per Garrett Cooper suggestion.
Also I want to add that I came to this question while observing behavior
consistent with multiple wakeup on FreeBSD-8.1. The heavily
multi-threaded code that assumes that only one thread can be woken up by
one
On Wed Feb 23 11, Garrett Cooper wrote:
On Wed, Feb 23, 2011 at 3:53 PM, Alexander Best arun...@freebsd.org wrote:
On Wed Feb 23 11, Garrett Cooper wrote:
On Feb 22, 2011, at 9:51 AM, John Baldwin wrote:
On Tuesday, February 22, 2011 11:46:05 am Garrett Cooper wrote:
(Please bottom
On 2011/02/28 05:26, Yuri wrote:
Forwarding to standards@ and davidxu@ per Garrett Cooper suggestion.
Also I want to add that I came to this question while observing behavior
consistent with multiple wakeup on FreeBSD-8.1. The heavily
multi-threaded code that assumes that only one thread can
On Feb 27, 2011, at 4:26 PM, Yuri y...@rawbw.com wrote:
Forwarding to standards@ and davidxu@ per Garrett Cooper suggestion.
Also I want to add that I came to this question while observing behavior
consistent with multiple wakeup on FreeBSD-8.1. The heavily multi-threaded
code that
On Sunday 27 February 2011 22:26:18 Yuri wrote:
Also I want to add that I came to this question while observing behavior
consistent with multiple wakeup on FreeBSD-8.1. The heavily
multi-threaded code that assumes that only one thread can be woken up by
one pthread_cond_signal call crashes,
7 matches
Mail list logo
