David Chisnall

Hi, thanks for trying snmalloc! This is expected behaviour. `snmalloc` provides you with a lot of tools for building different allocators and not all consumers want to use it as...

The prefixing is controlled by the `SNMALLOC_STATIC_LIBRARY_PREFIX` cmake variable. If you set this to "" then you should have `malloc` and friends exposed from the static library. I don't know...

@nwf, the memcpy is currently incorrect for CHERI. It's probably worth tweaking the default one for any platform where the AAL says that it's CHERI and a specialising it for...

If it isn't a bottleneck then it's probably not worth the code size increase. It's small but a lot of small things add up.

Hi, I've thought about adding this API. I think the correct way of doing it is: - Extend the PALs to support no-core memory as a class-template parameter. - Create...

Hi, most of these changes seem to be replacing stdio with iostreams. Can you pull those out into a separate PR? Are those things necessary for MinGW or just cleanups?

I'm not a huge fan of the `FORTIFY_SOURCE` approach because it doesn't catch any bugs that the clang static analyser doesn't also catch. When I asked Google's security team why...

> If the compiler can eliminate sufficiently many checks, then for some instances, the cost of the checks being an additional function call could be mitigated, but we would have...

@rengolin, a few comments: > The new builtin will definitely be a dynamic check, but it should be forced inline and super simple (ex. load a value from a global...

If you're statically linking then, before you strip the binary, running `nm` and seeing if you see any snmalloc symbols will let you see if you've pulled it in (which...