https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2018-08-14T08:38:00+00:00 2018-08-14T08:38:00+00:00 David Wood david@davidtw.co 2018-08-08T12:28:26+00:00 urn:sha1:b16a30677f4e641329e768272cf9d3ecc2fa31c4 2018-06-03T11:46:19+00:00 Jorge Aparicio jorge@japaric.io 2018-04-30T08:55:24+00:00 urn:sha1:e44ad61a2d8e3bac1d2cbf2467a7202250b8a77e 2018-01-26T02:11:42+00:00 Alex Crichton alex@alexcrichton.com 2018-01-26T02:11:42+00:00 urn:sha1:6e1cebb387fdae0d436d477697e3a2aae7c3772c 2018-01-02T13:11:41+00:00 Ed Schouten ed@nuxi.nl 2018-01-02T13:11:41+00:00 urn:sha1:3f880912e90825a88b0a25e235dd43b24da1055b 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-11-28T17:27:35+00:00 Alex Crichton alex@alexcrichton.com 2017-11-26T18:39:16+00:00 urn:sha1:73970bf6f287b93ebd9775783652217e1aca02d3 This commit allocates a builder to running wasm32 tests on Travis. Not all test suites pass right now so this is starting out with just the run-pass and the libcore test suites. This'll hopefully give us a pretty broad set of coverage for integration in rustc itself as well as a somewhat broad coverage of the llvm backend itself through integration/unit tests. 2017-01-19T21:54:19+00:00 Alex Crichton alex@alexcrichton.com 2017-01-17T07:10:00+00:00 urn:sha1:e8f9d2d43a190074d52a0df40725ebd2c0fb0a9e This commit adds a new entry to the Travis matrix which will execute emscripten test suites. Along the way it updates a few bits of the test suite to continue passing on emscripten, such as: * Ignoring i128/u128 tests as they're presumably just not working (didn't investigate as to why) * Disabling a few process tests (not working on emscripten) * Ignore some num tests in libstd (#39119) * Fix some warnings when compiling 2017-01-12T22:53:02+00:00 est31 MTest31@outlook.com 2017-01-11T01:25:44+00:00 urn:sha1:6a29fab274ff72e429b9d323f204a0617d53d8e3 Now, no feature outside of the whitelist is without a test marked as its gate test. 2016-05-09T15:22:36+00:00 Alex Crichton alex@alexcrichton.com 2016-04-08T23:18:40+00:00 urn:sha1:0ec321f7b541fcbfbf20286beb497e6d9d3352b2 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).