Searched hist:213241 (Results 1 - 6 of 6) sorted by relevance
/freebsd-10.2-release/lib/libthr/thread/ | ||
H A D | thr_rwlock.c | diff 213241 Tue Sep 28 05:01:28 MDT 2010 davidxu In current code, statically initialized and destroyed object have same null value, the code can not distinguish between them, to fix the problem, now a destroyed object is assigned to a non-null value, and it will be rejected by some pthread functions. PTHREAD_ADAPTIVE_MUTEX_INITIALIZER_NP is changed to number 1, so that adaptive mutex can be statically initialized correctly. |
H A D | thr_cond.c | diff 213241 Tue Sep 28 05:01:28 MDT 2010 davidxu In current code, statically initialized and destroyed object have same null value, the code can not distinguish between them, to fix the problem, now a destroyed object is assigned to a non-null value, and it will be rejected by some pthread functions. PTHREAD_ADAPTIVE_MUTEX_INITIALIZER_NP is changed to number 1, so that adaptive mutex can be statically initialized correctly. |
H A D | thr_init.c | diff 213241 Tue Sep 28 05:01:28 MDT 2010 davidxu In current code, statically initialized and destroyed object have same null value, the code can not distinguish between them, to fix the problem, now a destroyed object is assigned to a non-null value, and it will be rejected by some pthread functions. PTHREAD_ADAPTIVE_MUTEX_INITIALIZER_NP is changed to number 1, so that adaptive mutex can be statically initialized correctly. |
H A D | thr_mutex.c | diff 213241 Tue Sep 28 05:01:28 MDT 2010 davidxu In current code, statically initialized and destroyed object have same null value, the code can not distinguish between them, to fix the problem, now a destroyed object is assigned to a non-null value, and it will be rejected by some pthread functions. PTHREAD_ADAPTIVE_MUTEX_INITIALIZER_NP is changed to number 1, so that adaptive mutex can be statically initialized correctly. |
H A D | thr_private.h | diff 213241 Tue Sep 28 05:01:28 MDT 2010 davidxu In current code, statically initialized and destroyed object have same null value, the code can not distinguish between them, to fix the problem, now a destroyed object is assigned to a non-null value, and it will be rejected by some pthread functions. PTHREAD_ADAPTIVE_MUTEX_INITIALIZER_NP is changed to number 1, so that adaptive mutex can be statically initialized correctly. |
/freebsd-10.2-release/include/ | ||
H A D | pthread.h | diff 213241 Tue Sep 28 05:01:28 MDT 2010 davidxu In current code, statically initialized and destroyed object have same null value, the code can not distinguish between them, to fix the problem, now a destroyed object is assigned to a non-null value, and it will be rejected by some pthread functions. PTHREAD_ADAPTIVE_MUTEX_INITIALIZER_NP is changed to number 1, so that adaptive mutex can be statically initialized correctly. |
Completed in 137 milliseconds