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

Age	Commit message (Collapse)	Author	Lines
2020-07-27	mv std libs to library/	mark	-292/+0

2019-12-22	Format the world	Mark Rousskov	-22/+21

2019-11-26	Fix spelling typos	Brian Wignall	-1/+1

2019-11-03	Allow foreign exceptions to unwind through Rust code	Amanieu d'Antras	-4/+11

2019-08-02	libpanic_unwind: Unconfigure tests during normal build	Vadim Petrochenkov	-18/+22

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

2019-02-10	rustc: doc comments	Alexander Regueiro	-2/+2

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

2018-12-07	Various minor/cosmetic improvements to code	Alexander Regueiro	-1/+1

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

2018-08-20	Replace usages of ptr::offset with ptr::{add,sub}.	Corey Farwell	-1/+1

2018-07-11	Deny bare trait objects in in src/libpanic_unwind	ljedrz	-2/+2

2017-06-08	std: Avoid panics in rust_eh_personality	Alex Crichton	-23/+32
	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	-7/+3

2016-07-26	Fix typos	Vadim Chugunov	-1/+1

2016-07-25	Looser LSDA parsing	Vadim Chugunov	-4/+3

2016-07-22	Implement rust_eh_personality in Rust, remove rust_eh_personality_catch.	Vadim Chugunov	-35/+72
	Well, not quite: ARM EHABI platforms still use the old scheme -- for now.
2016-06-05	run rustfmt on libpanic_unwind folder	Srinivas Reddy Thatiparthy	-54/+51

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