[PATCH] Re: Found? Re: [Gc] Assertion failure in GC_malloc_uncollectabl

[Jan Wielemaker]

On 05/15/2012 11:21 AM, Ivan Maidanski wrote:
>> My motivation to move this into GC_malloc_generic() was twofold:
>> clearly
>>> GC can come in between and it seems a waste to acquire the lock
>>> twice for a single operation with only a few unlocked
>>> instructions in between.

> I understand. But, the other alternative is to use lock-less
> GC_generic_malloc_internal (not sure right now that its functionality
> is the same as GC_generic_malloc).

I leave that decision to the experts.  I'm happy to test.

> BTW. We should also fix GC_malloc_atomic_uncollectable.

Looks like it is doing the same thing.

Thanks for looking into this.  I still like to run with gc assertions
enabled as long as I'm developing.

		--- Jan