[M3commit] CVS Update: cm3

[Tony Hosking]

No, not really.  Recursive mutexes are not supported on all platforms.
Also, in the reql world we will avoid using mutexes in most instances, instead using lock reservation, etc.

Antony Hosking | Associate Professor | Computer Science | Purdue University
305 N. University Street | West Lafayette | IN 47907 | USA
Office +1 765 494 6001 | Mobile +1 765 427 5484




On Jan 11, 2011, at 8:58 PM, Jay K wrote:

> 
> We should use PTHREAD_MUTEX_RECURSIVE for the heap lock, and then dispense
> with most of the code implementing it, right?
> ie: no inCritical, no holder, no condition variables?
> 
> - Jay
> 
> 
> ----------------------------------------
>> Date: Wed, 12 Jan 2011 01:37:59 +0000
>> To: m3commit at elegosoft.com
>> From: hosking at elego.de
>> Subject: [M3commit] CVS Update: cm3
>> 
>> CVSROOT: /usr/cvs
>> Changes by: hosking at birch. 11/01/12 01:37:59
>> 
>> Modified files:
>> cm3/m3-libs/m3core/src/thread/PTHREAD/: ThreadPThread.m3
>> 
>> Log message:
>> Oops, so-called "fix" last night was completely broken (tired!).
>> [Mika, please try this latest]
>>