https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.12.1 2016-07-27T01:53:47+00:00 2016-07-27T01:53:47+00:00 Vadim Chugunov vadimcn@gmail.com 2016-07-27T01:53:47+00:00 urn:sha1:ec8518e4fbde1b578137883cc7c4fe6805723a3f 2016-07-25T16:37:41+00:00 Vadim Chugunov vadimcn@gmail.com 2016-07-25T05:09:56+00:00 urn:sha1:5fbcf08dd8cfc347c13d84c8ea20e3bfce6793fc 2016-07-22T21:58:35+00:00 Vadim Chugunov vadimcn@gmail.com 2016-07-22T21:57:54+00:00 urn:sha1:051c2d14fb1e73866376668088971605d38f0c65 Well, not quite: ARM EHABI platforms still use the old scheme -- for now. 2016-06-05T18:04:23+00:00 Srinivas Reddy Thatiparthy thatiparthysreenivas@gmail.com 2016-05-29T10:36:29+00:00 urn:sha1:00bbc27276a3696522aef1d66bcc955b8e862ae9 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).