Re: [PATCH] Re: Found? Re: [Gc] Assertion failure in GC_malloc_uncollectabl
ivmai at mail.ru
Tue May 15 03:39:44 PDT 2012
I'll spend more for this bug some days later and select the way to fix it.
Tue, 15 May 2012 12:00:52 +0200 Jan Wielemaker <J.Wielemaker at vu.nl>:
> 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
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc