joelsiks
JIT Compilers and Cache Coherency
Re:Meta’s Renewed Commitment to jemalloc
on Monday March 16, 2026 @04:14PM (#47404266)
Opening up strong with a gigantic merge of the stuff they've been working on in their own fork: https://github.com/jemalloc/jemalloc/pull/2863
Re:Why is the first C++ (m)allocation always 72 KB?
on Sunday March 01, 2026 @08:23AM (#47206484)
I did mention it briefly in the post, but you can opt-in for a fixed-size statically allocated buffer by configuring libstdc++ with --enable-libstdcxx-static-eh-pool. Also, you can opt-out of the pool entirely by configuring the number of objects in the pool to zero with the environment variable GLIBCXX_TUNABLES=glibcxx.eh_pool.obj_count=0.
Re:Why is the first C++ (m)allocation always 72 KB?
on Sunday March 01, 2026 @06:56AM (#47205922)
The exact implementation of mymalloc isn't relevant to the post. I have an old allocator published at https://github.com/joelsiks/jsmalloc that I did as part of my Master's thesis, which uses a similar debug-logging mechanism that is described in the post.