about summary refs log tree commit diff
path: root/src/rt/sync/rust_thread.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-10-18 15:26:24 -0700
committerbors <bors@rust-lang.org>2013-10-18 15:26:24 -0700
commitdf187a0b67cf94b339220c3fa7b9d2edbe4d05aa (patch)
tree46e01e5cc346070285c64a8bd68827cc5363f6dd /src/rt/sync/rust_thread.cpp
parent6b07d885f3dd1a80ffca113925a949386371ea97 (diff)
parent90911d72592fedbce0c34d8a0e20b5aac5c781bf (diff)
downloadrust-df187a0b67cf94b339220c3fa7b9d2edbe4d05aa.tar.gz
rust-df187a0b67cf94b339220c3fa7b9d2edbe4d05aa.zip
auto merge of #9933 : alexcrichton/rust/no-jemalloc, r=brson
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
Diffstat (limited to 'src/rt/sync/rust_thread.cpp')
0 files changed, 0 insertions, 0 deletions