https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.10.0 2016-05-31T23:29:53+00:00 2016-05-31T23:29:53+00:00 Alex Crichton alex@alexcrichton.com 2016-05-24T05:29:17+00:00 urn:sha1:18cb3ed35ac8e83c2d97d9996adab2b07e980e09 We've gotten requests to move our Android support as far back as API level 9 where unfortunately the `posix_memalign` API wasn't implemented yet. Thankfully, however, the `memalign` API was and it appears to be usable with `free` on the Android platform (see comments included in commit). This should help fix some of the last few test failures when compiling against API level 9. 2016-05-09T15:22:36+00:00 Alex Crichton alex@alexcrichton.com 2016-04-08T23:18:40+00:00 urn:sha1:0ec321f7b541fcbfbf20286beb497e6d9d3352b2 This commit is an implementation of [RFC 1513] which allows applications to alter the behavior of panics at compile time. A new compiler flag, `-C panic`, is added and accepts the values `unwind` or `panic`, with the default being `unwind`. This model affects how code is generated for the local crate, skipping generation of landing pads with `-C panic=abort`. [RFC 1513]: https://github.com/rust-lang/rfcs/blob/master/text/1513-less-unwinding.md Panic implementations are then provided by crates tagged with `#![panic_runtime]` and lazily required by crates with `#![needs_panic_runtime]`. The panic strategy (`-C panic` value) of the panic runtime must match the final product, and if the panic strategy is not `abort` then the entire DAG must have the same panic strategy. With the `-C panic=abort` strategy, users can expect a stable method to disable generation of landing pads, improving optimization in niche scenarios, decreasing compile time, and decreasing output binary size. With the `-C panic=unwind` strategy users can expect the existing ability to isolate failure in Rust code from the outside world. Organizationally, this commit dismantles the `sys_common::unwind` module in favor of some bits moving part of it to `libpanic_unwind` and the rest into the `panicking` module in libstd. The custom panic runtime support is pretty similar to the custom allocator support with the only major difference being how the panic runtime is injected (takes the `-C panic` flag into account). 2016-04-15T17:02:21+00:00 Alex Crichton alex@alexcrichton.com 2016-04-15T17:02:21+00:00 urn:sha1:99c05478542c6624d537f587ce34f84d09fd0627 The Unix implementation was incorrectly handling failure for reallocation of over-aligned types by not checking for NULL. Closes #32993 2016-02-11T19:12:32+00:00 Alex Crichton alex@alexcrichton.com 2016-01-21T23:19:23+00:00 urn:sha1:2581b141473f8333728c8dc330a31dc2373dc0e6 These describe the structure of all our crate dependencies. 2016-02-06T20:56:14+00:00 Brian Anderson banderson@mozilla.com 2015-11-26T19:05:10+00:00 urn:sha1:d6c0d859f6d859aa6e418b5ec58246071efbc9de Backtraces, and the compilation of libbacktrace for asmjs, are disabled. This port doesn't use jemalloc so, like pnacl, it disables jemalloc *for all targets* in the configure file. It disables stack protection. 2016-02-02T04:39:07+00:00 Alex Crichton alex@alexcrichton.com 2016-01-30T21:27:00+00:00 urn: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. 2016-01-25T04:35:55+00:00 Alex Crichton alex@alexcrichton.com 2016-01-21T23:26:19+00:00 urn: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 2016-01-13T01:39:00+00:00 Anton Blanchard anton@samba.org 2015-12-28T21:09:06+00:00 urn:sha1:b372910476c40584a22cd253c69106775d0c93fa This adds support for big endian and little endian PowerPC64. make check runs clean apart from one big endian backtrace issue. 2016-01-12T20:04:59+00:00 Tamir Duberstein tamird@gmail.com 2015-12-29T01:04:20+00:00 urn:sha1:5657eefcd8f976e2558d8eae47e73ddb2119ccba See: http://developer.android.com/ndk/downloads/revision_history.html Also, use `libc`'s `posix_memalign`. 2015-12-21T17:26:21+00:00 Alex Crichton alex@alexcrichton.com 2015-12-11T21:07:11+00:00 urn:sha1:cd1848a1a60f40f25019e455b1050efd69707604 Lots of cruft to remove!