Request for feedback on WG14 proposal N3849 (alloc_at_least)

Paul Eggert eggert@cs.ucla.edu
Thu Apr 23 17:21:04 GMT 2026


On 2026-04-23 09:43, Wilco Dijkstra wrote:
> However realloc is*fast* if the size fits or is a little smaller: it takes
> less than 5 cycles on a modern CPU (over 550 million calls per second).

Sure, but I was wondering not about microbenchmarks, but about realistic 
applications. That's a key point in determining the cost/benefit 
tradeoff for this proposal.

Clearly the main motivation for the proposal is performance, as realloc 
already provides the functionality needed for correctness. So, what 
performance costs and benefits would typical glibc-using apps see? 
That's not clear from the proposal.


More information about the Libc-alpha mailing list