Am 14.03.2012 17:44, schrieb Invisible:

> OK. Well typically each object has some overhead that tells you which
> class it belongs to. Typically the GC engine is going to go off that
> information, so you're arguably not adding any additional cost there.
> Typically each object just gets one pointer wider.
>
> Whether a static allocator can match that or not is open to debate. In
> particular, I'd imagine a static allocator might have O(N) cost per
> /free block/, whereas a typical GC implementation doesn't need to track
> free blocks at all...

If a GC implementation doesn't track free blocks, how is it ever going 
to re-allocate them to anything?

Post a reply to this message