Thread GC non "stop-the-world"

[Kagamin via Digitalmars-d]

On Thursday, 25 September 2014 at 21:59:15 UTC, Sean Kelly wrote:
> On Thursday, 25 September 2014 at 13:55:42 UTC, Wyatt wrote:
>>
>> The caveat for D being this design requires read and write 
>> barriers and I'm pretty sure I recall correctly that those 
>> have been vetoed several times for complexity.
>
> Pretty much for reasons of being able to call C functions and 
> inline asm code.  Memory barriers may still be possible in 
> these scenarios, but they would be extremely expensive.

BTW, C usually accepts data only for reading, and writes mostly 
strings and buffers - plain data without pointers. In both cases 
it doesn't need to notify GC (as far as I understand write 
barriers).