rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2019-11-03	Allow foreign exceptions to unwind through Rust code	Amanieu d'Antras	-127/+0

2019-10-22	Apply clippy::needless_return suggestions	Mateusz Mikuła	-1/+1

2019-02-13	libpanic_unwind => 2018	Mazdak Farrokhzad	-2/+2

2018-12-25	Remove licenses	Mark Rousskov	-10/+0

2018-11-06	refactor: use shorthand fields	teresy	-1/+1

2018-08-29	Replace usages of 'bad_style' with 'nonstandard_style'.	Corey Farwell	-1/+1
	`bad_style` is being deprecated in favor of `nonstandard_style`: - https://github.com/rust-lang/rust/issues/41646
2018-07-11	Deny bare trait objects in in src/libpanic_unwind	ljedrz	-3/+3

2018-04-05	Bump the bootstrap compiler to 1.26.0 beta	Alex Crichton	-2/+1
	Holy cow that's a lot of `cfg(stage0)` removed and a lot of new stable language features!
2018-02-20	make `#[unwind]` attribute specify expectations more clearly	Niko Matsakis	-1/+2
	You can now choose between the following: - `#[unwind(allowed)]` - `#[unwind(aborts)]` Per rust-lang/rust#48251, the default is `#[unwind(allowed)]`, though I think we should change this eventually.
2017-06-08	std: Avoid panics in rust_eh_personality	Alex Crichton	-4/+5
	This commit removes a few calls to panic and/or assert in `rust_eh_personality`. This function definitely can't itself panic (that'd probably segfault or do something else weird) and I was also noticing that a `pub extern fn foo() {}` cdylib was abnormally large. Turns out all that size was the panicking machinery brought in by the personality function! The change here is to return a `Result` internally so we can bubble up the fatal error, eventually translating to the appropriate error code for the libunwind ABI.
2016-10-18	run rustfmt on libpanic_unwind	Srinivas Reddy Thatiparthy	-1/+2

2016-08-19	Remove old stage0 compatibility	Brian Anderson	-15/+0

2016-07-24	Implement ARM personality routine in Rust.	Vadim Chugunov	-0/+1
	Remove the `eh_personality_catch` lang item. Use a simplified version of `cfg_if!` in libunwind.
2016-07-22	Implement rust_eh_personality in Rust, remove rust_eh_personality_catch.	Vadim Chugunov	-6/+13
	Well, not quite: ARM EHABI platforms still use the old scheme -- for now.
2016-07-12	Use `ptr::{null, null_mut}` instead of `0 as *{const, mut}`	Tobias Bucher	-1/+2

2016-06-05	run rustfmt on libpanic_unwind folder	Srinivas Reddy Thatiparthy	-21/+20

2016-05-09	rustc: Implement custom panic runtimes	Alex Crichton	-0/+142
	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).