rust/src/liballoc_jemalloc/lib.rs, branch 1.12.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.12.02016-06-05T06:09:17+00:00run rustfmt on liballoc_jemalloc folder2016-06-05T06:09:17+00:00Srinivas Reddy Thatiparthythatiparthysreenivas@gmail.com2016-06-05T06:09:17+00:00urn:sha1:adf2c432dcd3e121ccbd3904c92252b51aa110a5Fix alloc_jemalloc on windows gnu targets2016-05-01T12:16:06+00:00Oliver Middletonolliemail27@gmail.com2016-05-01T12:16:06+00:00urn:sha1:e8cbcef86e33b7d3ffeda9be8797eebaac3eac28
jemalloc prefixes the symbols by default on Windows so we need to account
for that to avoid link errors such as: `undefined reference to `mallocx'`
when using alloc_jemalloc.
Prefix jemalloc on DragonFly to prevent segfaults.2016-04-02T16:40:59+00:00Michael Neumannmneumann@ntecs.de2016-04-02T16:40:59+00:00urn:sha1:9f3de647326fbe50e0e283b9018ab7c41abccde3
Similar to commits ed015456a114ae907a36af80c06f81ea93182a24 (iOS)
and e3b414d8612314e74e2b0ebde1ed5c6997d28e8d (Android)
std: Prefix jemalloc symbols on iOS2016-02-18T00:24:00+00:00Alex Crichtonalex@alexcrichton.com2016-02-18T00:24:00+00:00urn:sha1:ed015456a114ae907a36af80c06f81ea93182a24
Similar to OSX, these symbols are prefixed by default.
std: Stop prefixing jemalloc symbols2016-02-14T19:50:40+00:00Alex Crichtonalex@alexcrichton.com2016-02-07T06:54:35+00:00urn:sha1:e3b414d8612314e74e2b0ebde1ed5c6997d28e8d
Now that we properly only link in jemalloc when building executables, we have
far less to worry about in terms of polluting the global namespace with the
`free` and `malloc` symbols on Linux. This commit will primarily allow LLVM to
use jemalloc so the compiler will only be using one allocator overall.
Locally this took compile time for libsyntax from 95 seconds to 89 (a 6%
improvement).
bootstrap: Add directives to not double-link libs2016-02-11T19:12:32+00:00Alex Crichtonalex@alexcrichton.com2016-01-21T23:36:25+00:00urn:sha1:eac0a8bc3070e45047fff57e7b024a059289a36d
Have all Cargo-built crates pass `--cfg cargobuild` and then add appropriate
`#[cfg]` definitions to all crates to avoid linking anything if this is passed.
This should help allow libstd to compile with both the makefiles and with Cargo.
target_arch is always powerpc64, remove powerpc64le check2016-02-09T20:09:40+00:00Anton Blanchardanton@samba.org2016-02-03T19:48:26+00:00urn:sha1:afdf179d84dc4aa290c38604b5f35b1ef669fd65
We no longer need to check for powerpc64le, so remove it.
Remove "powerpc64le" and "mipsel" target_arch2016-02-02T04:39:07+00:00Alex Crichtonalex@alexcrichton.com2016-01-30T21:27:00+00:00urn:sha1:8f803c202681fa137fca691df999ac3f335d29c1
Currently the `mipsel-unknown-linux-gnu` target doesn't actually set the
`target_arch` value to `mipsel` but it rather uses `mips`. Alternatively the
`powerpc64le` target does indeed set the `target_arch` as `powerpc64le`,
causing a bit of inconsistency between theset two.
As these are just the same instance of one instruction set, let's use
`target_endian` to switch between them and only set the `target_arch` as one
value. This should cut down on the number of `#[cfg]` annotations necessary and
all around be a little more ergonomic.
mk: Move from `-D warnings` to `#![deny(warnings)]`2016-01-25T04:35:55+00:00Alex Crichtonalex@alexcrichton.com2016-01-21T23:26:19+00:00urn:sha1:2273b5202354b3091f493cfcfa5bf48165e92b1e
This commit removes the `-D warnings` flag being passed through the makefiles to
all crates to instead be a crate attribute. We want these attributes always
applied for all our standard builds, and this is more amenable to Cargo-based
builds as well.
Note that all `deny(warnings)` attributes are gated with a `cfg(stage0)`
attribute currently to match the same semantics we have today
Add powerpc64 and powerpc64le support2016-01-13T01:39:00+00:00Anton Blanchardanton@samba.org2015-12-28T21:09:06+00:00urn:sha1:b372910476c40584a22cd253c69106775d0c93fa
This adds support for big endian and little endian PowerPC64.
make check runs clean apart from one big endian backtrace issue.