3 ms·
> What else do you need? A guarantee that this "allocator function" is only ever called once.
by ori_b 8y ago
> What else do you need?
A guarantee that this "allocator function" is only ever called once.
- xtrapolate 8y agoAre you seriously suggesting this is an issue? That's entirely up to you to solve in your custom allocator. Use whatever mechanism is available to you. Use a global condition variable, check it atomically every time you're entering your custom allocator, increment after a successful allocation. I don't know your system's constraints, nor should I...
- ori_b 8y agoI'm not talking about concurrency. I'm talking about needing to know exactly how many bytes are being allocated ahead of time, because I've got 192k of ram, and 112k of them are spoken for by I/O buffers. If I pass in an allocator that returns the statically allocated buffer, then the second call to it must abort loudly.