https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.26.2 2018-01-02T13:11:41+00:00 2018-01-02T13:11:41+00:00 Ed Schouten ed@nuxi.nl 2018-01-02T13:11:41+00:00 urn:sha1:3f880912e90825a88b0a25e235dd43b24da1055b It looks like many of these tests are already disabled on emscripten, which also doesn't seem to support environment variables and subprocess spawning. Just add a similar tag for CloudABI. While there, sort some of the lists of operating systems alphabetically. 2017-10-18T01:46:38+00:00 Alex Crichton alex@alexcrichton.com 2017-10-18T01:45:42+00:00 urn:sha1:d9ecdfe3a7a579b9ec89355168f13760c670d4d4 All tests should now have annotation for *why* they're ignored on emscripten. A few tests no longer need such an annotation as well! Closes #41299 2017-04-23T20:00:02+00:00 Tim Neumann mail@timnn.me 2017-04-02T09:24:22+00:00 urn:sha1:a146431e4c8095a3d809517c8abc6b886d5c5b07 2016-09-30T21:02:44+00:00 Ross Schulman ross@rbs.io 2016-09-06T00:00:09+00:00 urn:sha1:b2dfeac6907ab63a3261cfa66c04db239d138433 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).