jemallocator

jemallocator copied to clipboard

Add the usage instructions that are in README to top-level crate documentation

1

Those are useful and hard to find if you don’t read READMEs.

nagisa

gnzlbg

Re-enable windows tests

3

gnzlbg

Update jemalloc-sys to use jemalloc 5.2.1

1

Seems that this crate is a bit behind the latest version of [jemalloc](https://github.com/jemalloc/jemalloc/tree/5.2.1). Is there something blocking the update from 5.1 -> 5.2.1?

CJP10

Including jemallocator-global doesn't actually enable jemalloc on MacOS X

3

I took an existing program, added a dependency on `jemallocator-global` in its Cargo.toml, built it with `--release`, and ran it under a profiler (Instruments). Observed: The profiler found stacks under...

jorendorff

``` cargo:rerun-if-changed=../jemalloc-sys/src/lib.rs OPT_LEVEL = Some("0") HOST = Some("x86_64-apple-darwin") CC_x86_64-apple-darwin = None CC_x86_64_apple_darwin = None HOST_CC = None CC = None CFLAGS_x86_64-apple-darwin = None CFLAGS_x86_64_apple_darwin = None HOST_CFLAGS = None CFLAGS...

sfackler

sfackler

We should properly error about this in the `build.rs`, or at least produce a BIG warning that this target is not supported.

gnzlbg

Support release/debug build

10

Hi Debug feature is really useful. However looks like cargo currently does not support enabling/disabling features based on debug/release build mode. I'd like to have some workaround like some feature...

MageSlayer

malloc, calloc, ... should use the `#[allocator]` attribute

4

@alexcrichton `malloc`, `calloc`, etc. do not return a `noalias` pointer, I think they should use the `#[allocator]` attribute but that's currently super unstable. Any ideas ?

gnzlbg