2025-04-02 18:13:53 +03:00
|
|
|
// ignore-tidy-linelength
|
2024-02-16 20:02:50 +00:00
|
|
|
//@ build-fail
|
2025-04-02 18:13:53 +03:00
|
|
|
//@ compile-flags: --error-format=human
|
|
|
|
|
//@ error-pattern: the linked panic runtime `panic_runtime_unwind` is not compiled with this crate's panic strategy `abort`
|
2024-02-16 20:02:50 +00:00
|
|
|
//@ dont-check-compiler-stderr
|
|
|
|
|
//@ aux-build:panic-runtime-unwind.rs
|
|
|
|
|
//@ compile-flags:-C panic=abort
|
rustc: Implement custom panic runtimes
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-08 16:18:40 -07:00
|
|
|
|
|
|
|
|
extern crate panic_runtime_unwind;
|
|
|
|
|
|
|
|
|
|
fn main() {}
|
2025-03-29 02:41:32 +03:00
|
|
|
|
2025-04-02 18:13:53 +03:00
|
|
|
// FIXME: The first and third errors are target-dependent.
|
|
|
|
|
//FIXME~? ERROR cannot link together two panic runtimes: panic_unwind and panic_runtime_unwind
|
|
|
|
|
//FIXME~? ERROR the linked panic runtime `panic_runtime_unwind` is not compiled with this crate's panic strategy `abort`
|
|
|
|
|
//FIXME~? ERROR the crate `panic_unwind` requires panic strategy `unwind` which is incompatible with this crate's strategy of `abort`
|