90911d7259
As discovered in #9925, it turns out that we weren't using jemalloc on most platforms. Additionally, on some platforms we were using it incorrectly and mismatching the libc version of malloc with the jemalloc version of malloc. Additionally, it's not clear that using jemalloc is indeed a large performance win in particular situtations. This could be due to building jemalloc incorrectly, or possibly due to using jemalloc incorrectly, but it is unclear at this time. Until jemalloc can be confirmed to integrate correctly on all platforms and has verifiable large performance wins on platforms as well, it shouldn't be part of the default build process. It should still be available for use via the LD_PRELOAD trick on various architectures, but using it as the default allocator for everything would require guaranteeing that it works in all situtations, which it currently doesn't. Closes #9925 |
||
---|---|---|
.. | ||
clean.mk | ||
ctags.mk | ||
dist.mk | ||
docs.mk | ||
host.mk | ||
install.mk | ||
llvm.mk | ||
perf.mk | ||
platform.mk | ||
pp.mk | ||
rt.mk | ||
rustllvm.mk | ||
snap.mk | ||
stage0.mk | ||
target.mk | ||
tests.mk | ||
tools.mk |