Re:Once upon a time, memory allocators made sense
by cperciva on Monday January 18, 2016 @06:23PM
(#10927753)
No, I don't. If you look at the code in question, every time I expand an allocation I at least double it.
[ Parent
| on HN ]
Re:Once upon a time, memory allocators made sense
by acqq on Monday January 18, 2016 @06:29PM
(#10927776)
I'd expect that such growth seldom allows the realloc to remain in-place (unless it's the last thing allocated before and already in a big preallocated chunk of the allocator)? Have you observed what you then get in your program? Which allocator is used underneath?
Re:Once upon a time, memory allocators made sense
by cperciva on Monday January 18, 2016 @06:41PM
(#10927844)
I haven't looked. I use whatever allocator is in libc anyway, so it will depend on what platform you're running on.
At worst, using realloc produces the same results as malloc/memcpy/free. At best, it might save a memcpy. No harm in giving it that flexibility.