- 09 8月, 2019 40 次提交
-
-
由 Mazdak Farrokhzad 提交于
enable flt2dec tests in Miri With ldexp implemented (thanks to @christianpoveda), we can finally enable these tests in Miri. Well, most of them -- some are just too slow.
-
由 Mazdak Farrokhzad 提交于
Improve test output I'm continuing to improve the test output for liballoc and libcore
-
由 Mazdak Farrokhzad 提交于
Add tests for some ICEs Closes #43623 Closes #44405 r? @Centril
-
由 Mazdak Farrokhzad 提交于
Remove gensym in format_args This also fixes some things to allow us to export opaque macros from libcore: * Don't consider items that are only reachable through opaque macros as public/exported (so they aren't linted as needing docs) * Mark private items reachable from the root of libcore as unstable - they are now reachable (in principle) in other crates via macros in libcore r? @petrochenkov
-
由 Mazdak Farrokhzad 提交于
Check rustbook links on all platforms when running locally cc https://github.com/rust-lang/rust/issues/62739
-
由 Mazdak Farrokhzad 提交于
Deprecate `try!` macro Replaces #62077 Fixes rust-lang/rust-clippy#1361 Fixes #61000
-
由 Ralf Jung 提交于
-
由 Mateusz Mikuła 提交于
-
由 Ralf Jung 提交于
-
由 Sayan Nandan 提交于
Merge recent changes into master
-
由 Sayan Nandan 提交于
-
由 Sayan Nandan 提交于
-
由 Sayan Nandan 提交于
-
由 bors 提交于
Improve `ptr_rotate` performance, tests, and benches The corresponding issue is #61784. I am not actually sure if miri can handle the test, but I can change the commit if necessary.
-
由 Lzu Tao 提交于
-
由 Lzu Tao 提交于
-
由 BO41 提交于
Co-Authored-By: NMazdak Farrokhzad <twingoow@gmail.com> Co-Authored-By: NOliver Middleton <olliemail27@gmail.com>
-
由 bors 提交于
Rollup of 6 pull requests Successful merges: - #63162 (Miri tests: use xargo to build separate libstd) - #63289 (Don't recommend `extern crate` syntax) - #63373 (gitignore: add comment explaining policy) - #63374 (move of packed fields might or might not occur when they actually are sufficiently aligned) - #63381 (reduce visibility) - #63387 (Test interaction between `async { ... }` and `?`, `return`, and `break`) Failed merges: r? @ghost
-
由 Mazdak Farrokhzad 提交于
Test interaction between `async { ... }` and `?`, `return`, and `break` Per the second checkbox in https://github.com/rust-lang/rust/issues/62121#issuecomment-506884048, test that `async { .. }` blocks: 1. do not allow `break` expressions. 2. get targeted by `return` and not the parent function. 3. get targeted by `?` and not the parent function. Works towards resolving blockers in #63209. r? @cramertj
-
由 Mazdak Farrokhzad 提交于
reduce visibility r? @petrochenkov
-
由 Mazdak Farrokhzad 提交于
move of packed fields might or might not occur when they actually are sufficiently aligned See https://github.com/taiki-e/pin-project/pull/34, where it was pointed out that we actually don't move fields of 1-aligned types when dropping a packed struct -- but e.g. in a `packed(2)` struct, we don't do something similar for 2-aligned types. The code for that is [here](https://github.com/rust-lang/rust/blob/db7c773a6be2f050d1d1504763819ea3916f5428/src/librustc_mir/util/alignment.rs#L7).
-
由 Mazdak Farrokhzad 提交于
gitignore: add comment explaining policy Based on https://github.com/rust-lang/rust/pull/63307#issuecomment-518539503, I added a comment what I think should be gitignored and what not. This is just a proposal, obviously. Also see https://github.com/rust-lang/rust/pull/53768 for some more discussion. The summary is that if there are junk files that you create locally and are fine leaving around (such as `mir_dump`), git has the option for you to add them to `.git/info/exclude`. Others might prefer to keep their working dir clean of those same junk files, so we shouldn't just ignore them for everyone. I then also cleaned up a few more things, but there were many things that I had no idea where they came from so I didn't touch them.
-
由 Mazdak Farrokhzad 提交于
Don't recommend `extern crate` syntax `extern crate` syntax is not a good recommendation any more, so I've changed it to just print a suggested crate name.
-
由 Mazdak Farrokhzad 提交于
Miri tests: use xargo to build separate libstd This uses `cargo miri setup` to prepare the libstd that is used for testing Miri, instead of adjusting the entire bootstrap process to make sure the libstd that already gets built is fit for Miri. The issue with our current approach is that with `test-miri = true`, libstd and the test suite get built with `--cfg miri`, which e.g. means hashbrown uses no SIMD, and not all things are tested. Such global side-effects seem like footguns waiting to go off. On the other hand, the new approach means we install xargo as a side-effect of doing `./x.py test src/tools/miri`, which might be surprising, and we also both have to build xargo and another libstd which costs some extra time. Not sure if the tools builders have enough time budget for that. Maybe there is a way to cache xargo? We have to first first land https://github.com/rust-lang/miri/pull/870 in Miri and then update this PR to include that change (also to get CI to test Miri before bors), but I wanted to get the review started here. Cc @oli-obk (for Miri) @alexcrichton (for CI) @Mark-Simulacrum (for bootstrap) Fixes https://github.com/rust-lang/rust/issues/61833, fixes https://github.com/rust-lang/rust/issues/63219
-
由 Yuki Okushi 提交于
-
由 Yuki Okushi 提交于
-
由 Mazdak Farrokhzad 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-