2016-01-21 17:19:23 -06:00
|
|
|
[package]
|
|
|
|
|
authors = ["The Rust Project Developers"]
|
|
|
|
|
name = "std"
|
|
|
|
|
version = "0.0.0"
|
|
|
|
|
build = "build.rs"
|
|
|
|
|
|
|
|
|
|
[lib]
|
|
|
|
|
name = "std"
|
|
|
|
|
path = "lib.rs"
|
|
|
|
|
crate-type = ["dylib", "rlib"]
|
|
|
|
|
|
|
|
|
|
[dependencies]
|
|
|
|
|
alloc = { path = "../liballoc" }
|
|
|
|
|
alloc_jemalloc = { path = "../liballoc_jemalloc", optional = true }
|
|
|
|
|
alloc_system = { path = "../liballoc_system" }
|
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 18:18:40 -05:00
|
|
|
panic_unwind = { path = "../libpanic_unwind" }
|
|
|
|
|
panic_abort = { path = "../libpanic_abort" }
|
2016-01-21 17:19:23 -06:00
|
|
|
collections = { path = "../libcollections" }
|
|
|
|
|
core = { path = "../libcore" }
|
|
|
|
|
libc = { path = "../rustc/libc_shim" }
|
|
|
|
|
rand = { path = "../librand" }
|
|
|
|
|
rustc_unicode = { path = "../librustc_unicode" }
|
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 18:18:40 -05:00
|
|
|
unwind = { path = "../libunwind" }
|
2016-01-21 17:19:23 -06:00
|
|
|
|
|
|
|
|
[build-dependencies]
|
|
|
|
|
build_helper = { path = "../build_helper" }
|
2016-04-27 20:02:31 -05:00
|
|
|
gcc = "0.3.27"
|
2016-01-21 17:19:23 -06:00
|
|
|
|
|
|
|
|
[features]
|
2016-07-26 15:21:25 -05:00
|
|
|
backtrace = []
|
2016-01-21 17:19:23 -06:00
|
|
|
jemalloc = ["alloc_jemalloc"]
|
|
|
|
|
debug-jemalloc = ["alloc_jemalloc/debug"]
|
