Darren New wrote:
> Warp wrote:
>> There's basically no difference between GC'd and non-GC'd allocation.
> 
> This is incorrect. A GC allocation is adding the size of a structure to 
> the pointer, just like allocating something on the stack is. If you 
> can't move stuff around after it's allocated, it becomes extremely hard 
> to beat this speed.

Or, to phrase it a different way that might make it more clear...

How fast can you make your malloc() implementation if you know that 
nobody will ever call free()?  Pretty straightforward, given sbrk(), yes?

-- 
   Darren New / San Diego, CA, USA (PST)
     "That's pretty. Where's that?"
          "It's the Age of Channelwood."
     "We should go there on vacation some time."

Post a reply to this message