summary refs log tree commit diff
path: root/src/tools
AgeCommit message (Collapse)AuthorLines
2019-06-07bump clippyPietro Albini-14/+5
2019-05-20update miriRalf Jung-19/+5
2019-05-19Auto merge of #60065 - QuietMisdreavus:async-move-doctests, r=ollie27bors-1/+3
rustdoc: set the default edition when pre-parsing a doctest Fixes https://github.com/rust-lang/rust/issues/59313 (possibly more? i think we've had issues with parsing edition-specific syntax in doctests at some point) When handling a doctest, rustdoc needs to parse it beforehand, so that it can see whether it declares a `fn main` or `extern crate my_crate` explicitly. However, while doing this, rustdoc doesn't set the "default edition" used by the parser like the regular compilation runs do. This caused a problem when parsing a doctest with an `async move` block in it, since it was expecting the `move` keyword to start a closure, not a block. This PR changes the `rustdoc::test::make_test` function to set the parser's default edition while looking for a main function and `extern crate` statement. However, to do this, `make_test` needs to know what edition to set. Since this is also used during the HTML rendering process (to make playground URLs), now the HTML renderer needs to know about the default edition. Upshot: rendering standalone markdown files can now accept a "default edition" for their doctests with the `--edition` flag! (I'm pretty sure i waffled around how to set that a long time ago when we first added the `--edition` flag... `>_>`) I'm posting this before i stop for the night so that i can write this description while it's still in my head, but before this merges i want to make sure that (1) the `rustdoc-ui/failed-doctest-output` test still works (i expect it doesn't), and (2) i add a test with the sample from the linked issue.
2019-05-19Auto merge of #60946 - Xanewok:update-rls, r=oli-obkbors-0/+0
Update RLS Includes a fix (https://github.com/rust-lang/rls/pull/1462) for breakage due to Cargo update PR (https://github.com/rust-lang/rust/pull/60874) r? @Manishearth @oli-obk @ehuss
2019-05-19Auto merge of #60937 - RalfJung:miri, r=oli-obkbors-5/+19
update Miri r? @oli-obk
2019-05-18Update RLSIgor Matuszewski-0/+0
2019-05-18Update clippyManish Goregaokar-13/+10
2019-05-18update miriRalf Jung-5/+19
2019-05-17Auto merge of #60171 - matthewjasper:full-nll-compare-mode, r=pnkfelixbors-2/+1
Use -Zborrowck=mir for NLL compare mode closes #56993 r? @pnkfelix
2019-05-17Rollup merge of #60805 - euclio:filetime-dep, r=Mark-SimulacrumMazdak Farrokhzad-14/+17
remove compiletest's dependency on `filetime`
2019-05-17Rollup merge of #60685 - dtolnay:spdx, r=nikomatsakisMazdak Farrokhzad-5/+5
Switch to SPDX 2.1 license expression [According to the Cargo Reference:](https://doc.rust-lang.org/cargo/reference/manifest.html) > This is an SPDX 2.1 license expression for this package. Currently crates.io will validate the license provided against a whitelist of known license and exception identifiers from the SPDX license list 2.4. Parentheses are not currently supported. > > Multiple licenses can be separated with a \`/\`, although that usage is deprecated. Instead, use a license expression with AND and OR operators to get more explicit semantics. The notation with slashes is deprecated in favor of explicit AND or OR. As I understand it, Rust's license is MIT *OR* Apache-2.0 matching the meaning of *OR* defined by [SPDX Specification 2.1](https://spdx.org/spdx-specification-21-web-version): > If presented with a choice between two or more licenses, use the disjunctive binary "OR" operator to construct a new license expression, where both the left and right operands are valid license expression values.
2019-05-16Auto merge of #60888 - Manishearth:rollup-oihtoyq, r=Manishearthbors-7/+16
Rollup of 5 pull requests Successful merges: - #60207 (Outdent example, preserving nested fence) - #60278 (Document the `html_root_url` doc attribute value.) - #60597 (Do some simple constant propagation in the ConstProp pass) - #60837 (Update release notes for 1.35.0) - #60887 (Update clippy) Failed merges: r? @ghost
2019-05-16Update clippyManish Goregaokar-7/+16
2019-05-16Update cargoEric Huss-0/+0
2019-05-15Auto merge of #60775 - hellow554:no_bitrig, r=joshtriplettbors-6/+2
Remove bitrig support from rust Resolves #60743 using `find` and `rg` I delete every occurence of "bitrig" in the sources, expect for the llvm submodule (is this correct?). There's also this file https://github.com/rust-lang/rls/blob/5b8e99bb61958ca8abcb7c5eda70521726be1065/rls-analysis/test_data/rust-analysis/libstd-af9bacceee784405.json which contains a bitrig string in it. What to do with that?
2019-05-14Rollup merge of #60819 - matthiaskrgr:submodule_upd, r=oli-obkMazdak Farrokhzad-19/+7
submodules: update clippy from 3710ec59 to ad3269c4 Changes: ```` Rustfmt all the things Clippy dogfood Update for compiletest changes Use symbols instead of strings Rustup to rustc 1.36.0-nightly (1764b2972 2019-05-12) Add regression test for identity_conversion FP UI test cleanup: Extract many_single_char_names tests Add tests for empty_loop lint Add in_macro again Rename in_macro to in_macro_or_desugar ```` r? @oli-obk
2019-05-14submodules: update clippy from 3710ec59 to ad3269c4Matthias Krüger-19/+7
Changes: ```` Rustfmt all the things Clippy dogfood Update for compiletest changes Use symbols instead of strings Rustup to rustc 1.36.0-nightly (1764b2972 2019-05-12) Add regression test for identity_conversion FP UI test cleanup: Extract many_single_char_names tests Add tests for empty_loop lint Add in_macro again Rename in_macro to in_macro_or_desugar ````
2019-05-13remove compiletest's dependency on `filetime`Andy Russell-14/+17
2019-05-13update miriRalf Jung-19/+5
2019-05-13Remove bitrig support from rustMarcel Hellwig-6/+2
2019-05-12Change compare mode to use -Zborrowck=mirMatthew Jasper-2/+1
2019-05-12Auto merge of #60474 - mati865:musl_toolchain, r=alexcrichtonbors-1/+14
Make tests compatible with musl host As an alternative to passing explicit linker all over the place I could try linking `cc` to musl gcc since this bootstraps itself. Assigning for discussion: r? @alexcrichton
2019-05-11Update clippyManish Goregaokar-9/+17
2019-05-10Make tests compatible with musl hostMateusz Mikuła-1/+14
2019-05-10Auto merge of #60585 - sunfishcode:wasm32-wasi, r=alexcrichtonbors-1/+1
Omit the vendor component in the WASI triple This renames wasm32-unknown-wasi to wasm32-wasi, omitting the vendor component. This follows aarch64-linux-android, x86_64-fuchsia, and others in omitting the vendor field, which has the advantage of aligning with the [multiarch tuple](https://wiki.debian.org/Multiarch/Tuples), and of being less noisy. r? @alexcrichton
2019-05-09Switch to SPDX 2.1 license expressionDavid Tolnay-5/+5
According to the Cargo Reference: https://doc.rust-lang.org/cargo/reference/manifest.html > This is an SPDX 2.1 license expression for this package. Currently > crates.io will validate the license provided against a whitelist of > known license and exception identifiers from the SPDX license list > 2.4. Parentheses are not currently supported. > > Multiple licenses can be separated with a `/`, although that usage > is deprecated. Instead, use a license expression with AND and OR > operators to get more explicit semantics.
2019-05-09Omit the vendor component in the WASI tripleDan Gohman-1/+1
This renames wasm32-unknown-wasi to wasm32-wasi, omitting the vendor component. This follows aarch64-linux-android, x86_64-fuchsia, and others in omitting the vendor field, which has the advantage of aligning with the [multiarch tuple](https://wiki.debian.org/Multiarch/Tuples), and of being less noisy.
2019-05-09remove unneeded `extern crate`s from build toolsAndy Russell-14/+14
2019-05-08Auto merge of #60626 - matthiaskrgr:submodule_upd, r=oli-obkbors-9/+9
submodules: update clippy from fc96aa03 to 341c96af Fixes clippy toolstate Fixes https://github.com/rust-lang/rust/issues/60623 Changes: ```` rustup https://github.com/rust-lang/rust/pull/60586 Add test for #771. Clean up while_loop tests ```` r? @Manishearth
2019-05-08Auto merge of #60378 - froydnj:apple-target-modifications, r=michaelwoeristerbors-0/+11
conditionally modify darwin targets to macosx targets with versions We need this behavior so that Rust LLVM IR objects match the target triple for Clang LLVM IR objects. This matching then convinces the linker that yes, you really can do cross-language LTO with objects from different compilers. The newly-added tests seem to pass locally on x86_64-unknown-linux-gnu. I haven't done a full test run or tried the new compiler in an cross-language LTO setup yet.
2019-05-08submodules: update clippy from fc96aa03 to 341c96afMatthias Krüger-9/+9
Changes: ```` rustup https://github.com/rust-lang/rust/pull/60586 Add test for #771. Clean up while_loop tests ````
2019-05-07add negative tests for OS X LLVM target changesNathan Froyd-0/+11
2019-05-07Auto merge of #60596 - ehuss:update-cargo, r=alexcrichtonbors-0/+0
Update cargo 12 commits in beb8fcb5248dc2e6aa488af9613216d5ccb31c6a..759b6161a328db1d4863139e90875308ecd25a75 2019-04-30 23:58:00 +0000 to 2019-05-06 20:47:49 +0000 - Small things (rust-lang/cargo#6910) - Fix skipping over invalid registry packages (rust-lang/cargo#6912) - Fixes rust-lang/cargo#6874 (rust-lang/cargo#6905) - doc: Format examples of version to ease reading (rust-lang/cargo#6907) - fix more typos (codespell) (rust-lang/cargo#6903) - Parse less JSON on null builds (rust-lang/cargo#6880) - chore: Update opener to 0.4 (rust-lang/cargo#6902) - Update documentation for auto-discovery. (rust-lang/cargo#6898) - Update some doc links. (rust-lang/cargo#6897) - Default Cargo.toml template provide help for completing the metadata (rust-lang/cargo#6881) - Run 'cargo fmt --all' (rust-lang/cargo#6896) - Refactor command definition (rust-lang/cargo#6894)
2019-05-07Auto merge of #60464 - eddyb:not-overly-specific-pipelining, r=alexcrichtonbors-27/+41
rustc: rename -Z emit-directives to -Z emit-artifact-notifications and simplify the output. This is my take on #60006 / #60419 (see https://github.com/rust-lang/rust/pull/60006#discussion_r275983732). I'm not too attached the "notifications" part, it's pretty much bikeshed material. **EDIT**: for "artifact", @matklad pointed out Cargo already uses it (in https://github.com/rust-lang/rust/pull/60464#issuecomment-488576998) The first two commits are fixes that could be landed independently, especially the `compiletest` one, which removes the need for any of the normalization added in #60006 to land the test. The last commit enables the emission for all outputs, which was my main suggestion for #60006, mostly to show that it's minimal and not really a "scope creep" (as suggested in https://github.com/rust-lang/rust/pull/60006#discussion_r279964081). cc @alexcrichton @nnethercote
2019-05-07compiletest: uniformly normalize paths, so they all work on all platforms.Eduard-Mihai Burtescu-17/+15
2019-05-07rustc: rename -Z emit-directives to -Z emit-artifact-notifications and ↵Eduard-Mihai Burtescu-5/+5
simplify the output.
2019-05-07compiletest: only use `make_exe_name` for tests that end up being executed.Eduard-Mihai Burtescu-5/+21
2019-05-06Update cargoEric Huss-0/+0
2019-05-07Auto merge of #60531 - Centril:sort-features, r=oli-obkbors-4/+4
Enforce sorting of accepted and removed features Fixes https://github.com/rust-lang/rust/issues/60361 with mechanism introduced in https://github.com/rust-lang/rust/pull/60373. r? @oli-obk
2019-05-06set the default edition when pre-parsing a doctestQuietMisdreavus-1/+3
2019-05-06Auto merge of #60436 - Xanewok:update-rls, r=Manishearthbors-0/+0
Update RLS and Cargo Fixes the `test-fail` RLS toolstate caused by #59114. r? @Centril @Manishearth
2019-05-04Auto merge of #60538 - matthiaskrgr:submodule_upd, r=eddybbors-8/+10
submodules: update clippy from 2ed0b3bf to fc96aa03 Changes: ```` Rustup to rustc 1.36.0-nightly (13fde05b1 2019-05-03) Fix link in into_iter_on_array documentation remove function body from "too many args" span check closure arguments before use it format code fix suggestion for search_is_some fix suggestion for search_is_some naively change |&x| to |x| in stderr file cargo fmt useless_let_if_seq handle interior mutability ```` Fixes https://github.com/rust-lang/rust/issues/60534
2019-05-04submodules: update clippy from 2ed0b3bf to fc96aa03Matthias Krüger-8/+10
Changes: ```` Rustup to rustc 1.36.0-nightly (13fde05b1 2019-05-03) Fix link in into_iter_on_array documentation remove function body from "too many args" span check closure arguments before use it format code fix suggestion for search_is_some fix suggestion for search_is_some naively change |&x| to |x| in stderr file cargo fmt useless_let_if_seq handle interior mutability ````
2019-05-04Rename 'no tracking issue START' to fit better with tidy.Mazdak Farrokhzad-4/+4
2019-05-03tidy: Extract `let mut part` out of `parts` block in `version.rs`Alexey Shmalko-7/+5
2019-05-03Migrate tidy to rust 2018 editionAlexey Shmalko-10/+3
2019-05-03Rollup merge of #60373 - rasendubi:lang-features-sort-since, r=CentrilMazdak Farrokhzad-30/+192
Tidy: ensure lang features are sorted by since This is the tidy side of https://github.com/rust-lang/rust/issues/60361. What is left is actually splitting features into groups and sorting by since. This PR also likely to produce a small (a couple of lines) merge conflict with https://github.com/rust-lang/rust/pull/60362. r? @Centril
2019-05-02Make tidy::version::Version copyAlexey Shmalko-4/+4
2019-05-02Make in_feature_group a simple bool flagAlexey Shmalko-7/+6
2019-05-02Rework Version::parse to avoid extra allocationsAlexey Shmalko-10/+20
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-06 15:21:05 +0000