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

Age	Commit message (Collapse)	Author	Lines
2018-12-25	Remove licenses	Mark Rousskov	-70/+0

2018-09-26	Add `#![allow(..)]` as necessary to get re-migrated run-pass tests compiling ↵	Felix S. Klock II	-3/+4
	with clean stderr again. Most were added mechanically.
2018-09-26	Migrate `src/test/ui/run-pass/*` back to `src/test/run-pass/`.	Felix S. Klock II	-0/+258
	Fix #54047
2018-09-06	Migrated remaining `src/test/run-pass/` subdirectories to ↵	Felix S. Klock II	-246/+0
	`src/test/ui/run-pass/`.
2018-08-05	Fix stage 2 tests	varkor	-0/+3

2018-08-05	Remove panic-runtime opt-out	varkor	-9/+0

2018-08-05	Fix test/run-pass	varkor	-2/+10

2018-01-02	Add 'ignore-cloudabi' to tests that don't and won't build on CloudABI.	Ed Schouten	-0/+4
	It looks like many of these tests are already disabled on emscripten, which also doesn't seem to support environment variables and subprocess spawning. Just add a similar tag for CloudABI. While there, sort some of the lists of operating systems alphabetically.
2017-10-17	test: Update Emscripten failures/passing	Alex Crichton	-4/+4
	All tests should now have annotation for why they're ignored on emscripten. A few tests no longer need such an annotation as well! Closes #41299
2017-04-23	FIN: disable backtrace printing for panic-runtime/abort* on ARM	Tim Neumann	-2/+21

2016-09-30	Adding ignore-emscripten to failing tests.	Ross Schulman	-0/+4

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