Why is the first C++ (m)allocation always 72 KB? (joelsiks.com) | HN Screenshots

YHacker Newsscreenshots

Screenshot of joelsiks.com: Why is the first C++ (m)allocation always 72 KB?

First screen, captured 7 months ago.

Looks similar

Screenshot of evanjones.ca: The C Standard Library Function Isspace() Depends on Locale

The C Standard Library Function Isspace() Depends on Locale (evanjones.ca)

65 points by jandeboevrie 3 years ago | 51 comments

Screenshot of 8dcc.github.io: Writing a simple pool allocator in C

Writing a simple pool allocator in C (8dcc.github.io)

283 points by 8dcc 1 year ago | 118 comments

Screenshot of veera.app: Understanding Mesh Allocator

Understanding Mesh Allocator (veera.app)

60 points by signa11 2 years ago | 10 comments

Screenshot of nullprogram.com: So you want custom allocator support in your C library

So you want custom allocator support in your C library (nullprogram.com)

157 points by nalgeon 2 years ago | 91 comments

Screenshot of memo.barrucadu.co.uk: C is not Turing-complete (2018)

C is not Turing-complete (2018)(memo.barrucadu.co.uk)

8 points by xx_ns 2 years ago | 12 comments

Screenshot of joelsiks.com: How ZGC allocates memory for the Java heap

How ZGC allocates memory for the Java heap (joelsiks.com)

61 points by lichtenberger 1 year ago | 8 comments