davidxu 7218f7cbc7 Some software think a mutex can be destroyed after it owned it, for ... example, it uses a serialization point like following: pthread_mutex_lock(&mutex); pthread_mutex_unlock(&mutex); pthread_mutex_destroy(&muetx); They think a previous lock holder should have already left the mutex and is no longer referencing it, so they destroy it. To be maximum compatible with such code, we use IA64 version to unlock the mutex in kernel, remove the two steps unlocking code.		2012-03-18 00:22:29 +00:00
..
arch	- Switch to saving non-offseted pointer to TLS block in order too keep things simple	2012-03-06 03:27:58 +00:00
support	Merge from tbemd, with a small amount of rework:	2010-09-13 01:43:10 +00:00
sys
thread	Some software think a mutex can be destroyed after it owned it, for	2012-03-18 00:22:29 +00:00
libthr.3	mdoc: order prologue macros consistently by Dd/Dt/Os	2010-04-14 19:08:06 +00:00
Makefile	Oops, don't remove -fexceptions flag.	2010-10-08 01:53:33 +00:00
pthread.map	Introduce a non-portable function pthread_getthreadid_np(3) to retrieve	2011-02-07 21:26:46 +00:00