Matthew Parkinson
Matthew Parkinson
Should this be closed now?
This has been done in other PRs now.
> 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. I'll close, we can always...
It looks like the CLEAN_POINTER changes all made it into #528, and the rest has been superseeded by #537, so I am going to close this.
I don't believe mimalloc is unmaintained. @daanx is out of office at the moment so I can't double check with him. But generally he does a big push on mimalloc...
@osevan it is a while since I read the scalloc paper. If you could say a bit more about your suggestion that would be helpful. Also, could you share the...
If you are interested in adding security related features, you might want to look at some of the research we have done on snmalloc: https://github.com/microsoft/snmalloc/blob/main/docs/security/README.md Most of the ideas are...
Most allocators depend very little on libc. Even though snmalloc is written in C++ it doesn't need a C++ library at runtime. If you want to LD_PRELOAD, then you can't...
So would ```C++ ... auto end = pointer_offset(base, length); base = pointer_align_up(base, bits::one_at_bit(MIN_BITS)); end = pointer_align_down(end, bits::one_at_bit(MIN_BITS)); length = pointer_diff(base, end); if (base >= end) return; bool first = true;...
> Does missing the call to `f` potentially have consequences in those cases? It shouldn't mater if we don't call `f`. It should be callable multiple times, and zero. >...