[M3commit] CVS Update: cm3

[Tony Hosking]

The original intent was to have the heap all ready *before* threads  
were initialized so that there is no need for guards.  I haven't  
looked at your changes that split up the heap initialization.   
Installing the sanity check probably does need to be guarded in a  
multi-threaded world.  Fix is to invoke RTOS.LockHeap()/UnlockHeap()  
at begin/end of InstallSanityCheck.

On 20 Aug 2009, at 06:44, Jay K wrote:

> Does this need guards for thread safety?
> I considered some sort of "UntracedMonitor" but that would be a bit  
> larger.
> A special case for the sanity check might also be worthwhile?
>
>
> - Jay
>
>
>
> ----------------------------------------
>> Date: Thu, 20 Aug 2009 12:40:31 +0000
>> To: m3commit at elegosoft.com
>> From: jkrell at elego.de
>> Subject: [M3commit] CVS Update: cm3
>>
>> CVSROOT: /usr/cvs
>> Changes by: jkrell at birch. 09/08/20 12:40:31
>>
>> Modified files:
>> cm3/m3-libs/m3core/src/runtime/common/: RTCollector.m3
>> RTHeapRep.i3 RTLinker.m3
>>
>> Log message:
>> split up initialization so that the later part can do a traced  
>> allocation
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3commit/attachments/20090820/7a974e83/attachment-0002.html>