From 5a9807742b1cf626ef730df1f9ca53097aa14b3e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Ber=C3=A1nek?= Date: Sat, 28 Feb 2026 20:50:05 +0100 Subject: [PATCH 01/25] Mention `@bors squash` in squashing documentation --- src/doc/rustc-dev-guide/src/git.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/doc/rustc-dev-guide/src/git.md b/src/doc/rustc-dev-guide/src/git.md index bf31e79a9a154..34e419fa52259 100644 --- a/src/doc/rustc-dev-guide/src/git.md +++ b/src/doc/rustc-dev-guide/src/git.md @@ -383,6 +383,11 @@ Both the upside and downside of this is that it simplifies the history. On the one hand, you lose track of the steps in which changes were made, but the history becomes easier to work with. +The easiest way to squash your commits in a PR on the `rust-lang/rust` repository is to use the `@bors squash` command in a comment on the PR. By default, [bors] combines all commit messages of the PR into the squashed commit message. To customize the commit message, use `@bors squash msg=`. + + +If you want to squash commits using local git operations, read on below. + If there are no conflicts and you are just squashing to clean up the history, use `git rebase --interactive --keep-base main`. This keeps the fork point of your PR the same, making it easier to review the diff of what happened @@ -410,11 +415,6 @@ because they only represent "fixups" and not real changes. For example, `git rebase --interactive HEAD~2` will allow you to edit the two commits only. -For pull requests in `rust-lang/rust`, you can ask [bors] to squash by commenting -`@bors squash` on the PR. -By default, [bors] combines all commit messages in the PR. -To customize the commit message, use `@bors squash [msg|message=]`. - [bors]: https://github.com/rust-lang/bors ### `git range-diff` From 0b9fb671d8cef497beff74766ce1d14acedd6968 Mon Sep 17 00:00:00 2001 From: The rustc-josh-sync Cronjob Bot Date: Mon, 2 Mar 2026 04:40:37 +0000 Subject: [PATCH 02/25] Prepare for merging from rust-lang/rust This updates the rust-version file to e7d90c695a39426baf5ae705de2f9570a72229de. --- src/doc/rustc-dev-guide/rust-version | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/rustc-dev-guide/rust-version b/src/doc/rustc-dev-guide/rust-version index b6e1b2bc55df4..4dedd81b00666 100644 --- a/src/doc/rustc-dev-guide/rust-version +++ b/src/doc/rustc-dev-guide/rust-version @@ -1 +1 @@ -c78a29473a68f07012904af11c92ecffa68fcc75 +e7d90c695a39426baf5ae705de2f9570a72229de From 1f94e979fb9b09f4df5483ce549fb96574be1e6e Mon Sep 17 00:00:00 2001 From: Nicholas Nethercote Date: Wed, 22 Oct 2025 14:28:05 +1100 Subject: [PATCH 03/25] Fix some comments about dataflow analysis. Mostly in the examples in `initialized.rs`. In particular, the `EverInitializedPlaces` example currently doesn't cover how it's initialization sites that are tracked, rather than local variables (that's the `b_0`/`b_1` distinction in the example.) --- compiler/rustc_middle/src/mir/basic_blocks.rs | 2 +- .../src/impls/initialized.rs | 54 ++++++++++--------- 2 files changed, 29 insertions(+), 27 deletions(-) diff --git a/compiler/rustc_middle/src/mir/basic_blocks.rs b/compiler/rustc_middle/src/mir/basic_blocks.rs index aae815c0be046..bd8c022ef42a6 100644 --- a/compiler/rustc_middle/src/mir/basic_blocks.rs +++ b/compiler/rustc_middle/src/mir/basic_blocks.rs @@ -65,7 +65,7 @@ impl<'tcx> BasicBlocks<'tcx> { /// Returns basic blocks in a reverse postorder. /// - /// See [`traversal::reverse_postorder`]'s docs to learn what is preorder traversal. + /// See [`traversal::reverse_postorder`]'s docs to learn what is postorder traversal. /// /// [`traversal::reverse_postorder`]: crate::mir::traversal::reverse_postorder #[inline] diff --git a/compiler/rustc_mir_dataflow/src/impls/initialized.rs b/compiler/rustc_mir_dataflow/src/impls/initialized.rs index 6a0881ec2bcb8..f83ea0c8be61d 100644 --- a/compiler/rustc_mir_dataflow/src/impls/initialized.rs +++ b/compiler/rustc_mir_dataflow/src/impls/initialized.rs @@ -108,21 +108,21 @@ impl<'tcx> MaybePlacesSwitchIntData<'tcx> { /// ```rust /// struct S; /// #[rustfmt::skip] -/// fn foo(pred: bool) { // maybe-init: -/// // {} -/// let a = S; let mut b = S; let c; let d; // {a, b} +/// fn foo(p: bool) { // maybe-init: +/// // {p} +/// let a = S; let mut b = S; let c; let d; // {p, a, b} /// -/// if pred { -/// drop(a); // { b} -/// b = S; // { b} +/// if p { +/// drop(a); // {p, b} +/// b = S; // {p, b} /// /// } else { -/// drop(b); // {a} -/// d = S; // {a, d} +/// drop(b); // {p, a} +/// d = S; // {p, a, d} /// -/// } // {a, b, d} +/// } // {p, a, b, d} /// -/// c = S; // {a, b, c, d} +/// c = S; // {p, a, b, c, d} /// } /// ``` /// @@ -198,11 +198,11 @@ impl<'a, 'tcx> HasMoveData<'tcx> for MaybeInitializedPlaces<'a, 'tcx> { /// ```rust /// struct S; /// #[rustfmt::skip] -/// fn foo(pred: bool) { // maybe-uninit: +/// fn foo(p: bool) { // maybe-uninit: /// // {a, b, c, d} /// let a = S; let mut b = S; let c; let d; // { c, d} /// -/// if pred { +/// if p { /// drop(a); // {a, c, d} /// b = S; // {a, c, d} /// @@ -278,34 +278,36 @@ impl<'tcx> HasMoveData<'tcx> for MaybeUninitializedPlaces<'_, 'tcx> { } } -/// `EverInitializedPlaces` tracks all places that might have ever been -/// initialized upon reaching a particular point in the control flow -/// for a function, without an intervening `StorageDead`. +/// `EverInitializedPlaces` tracks all initializations that may have occurred +/// upon reaching a particular point in the control flow for a function, +/// without an intervening `StorageDead`. /// /// This dataflow is used to determine if an immutable local variable may /// be assigned to. /// /// For example, in code like the following, we have corresponding -/// dataflow information shown in the right-hand comments. +/// dataflow information shown in the right-hand comments. Underscored indices +/// are used to distinguish between multiple initializations of the same local +/// variable, e.g. `b_0` and `b_1`. /// /// ```rust /// struct S; /// #[rustfmt::skip] -/// fn foo(pred: bool) { // ever-init: -/// // { } -/// let a = S; let mut b = S; let c; let d; // {a, b } +/// fn foo(p: bool) { // ever-init: +/// // {p, } +/// let a = S; let mut b = S; let c; let d; // {p, a, b_0, } /// -/// if pred { -/// drop(a); // {a, b, } -/// b = S; // {a, b, } +/// if p { +/// drop(a); // {p, a, b_0, } +/// b = S; // {p, a, b_0, b_1, } /// /// } else { -/// drop(b); // {a, b, } -/// d = S; // {a, b, d } +/// drop(b); // {p, a, b_0, b_1, } +/// d = S; // {p, a, b_0, b_1, d} /// -/// } // {a, b, d } +/// } // {p, a, b_0, b_1, d} /// -/// c = S; // {a, b, c, d } +/// c = S; // {p, a, b_0, b_1, c, d} /// } /// ``` pub struct EverInitializedPlaces<'a, 'tcx> { From fcfd96e821339803350bef5ae702c72d85768e75 Mon Sep 17 00:00:00 2001 From: Guillaume Date: Sat, 7 Mar 2026 10:14:23 +0100 Subject: [PATCH 04/25] Fix LegacyKeyValueFormat report from docker build: pr --- src/ci/docker/host-x86_64/pr-check-1/Dockerfile | 4 ++-- src/ci/docker/host-x86_64/pr-check-2/Dockerfile | 5 ++--- src/ci/docker/host-x86_64/tidy/Dockerfile | 4 ++-- 3 files changed, 6 insertions(+), 7 deletions(-) diff --git a/src/ci/docker/host-x86_64/pr-check-1/Dockerfile b/src/ci/docker/host-x86_64/pr-check-1/Dockerfile index c1742720f7789..a595a079b48f1 100644 --- a/src/ci/docker/host-x86_64/pr-check-1/Dockerfile +++ b/src/ci/docker/host-x86_64/pr-check-1/Dockerfile @@ -39,7 +39,7 @@ COPY host-x86_64/pr-check-1/validate-toolstate.sh /scripts/ # Check library crates on all tier 1 targets. # We disable optimized compiler built-ins because that requires a C toolchain for the target. # We also skip the x86_64-unknown-linux-gnu target as it is well-tested by other jobs. -ENV SCRIPT \ +ENV SCRIPT=" \ # Check some tools that aren't included in `x check` by default, to # ensure that maintainers can still do check builds locally. python3 ../x.py check \ @@ -58,4 +58,4 @@ ENV SCRIPT \ python3 ../x.py check --set build.optimized-compiler-builtins=false core alloc std --target=aarch64-unknown-linux-gnu,i686-pc-windows-msvc,i686-unknown-linux-gnu,x86_64-apple-darwin,x86_64-pc-windows-gnu,x86_64-pc-windows-msvc && \ /scripts/validate-toolstate.sh && \ reuse --include-submodules lint && \ - python3 ../x.py test collect-license-metadata + python3 ../x.py test collect-license-metadata" diff --git a/src/ci/docker/host-x86_64/pr-check-2/Dockerfile b/src/ci/docker/host-x86_64/pr-check-2/Dockerfile index 885bf0b30b18c..6b843a6247e89 100644 --- a/src/ci/docker/host-x86_64/pr-check-2/Dockerfile +++ b/src/ci/docker/host-x86_64/pr-check-2/Dockerfile @@ -30,8 +30,7 @@ ENV RUST_CONFIGURE_ARGS="--set rust.validate-mir-opts=3" COPY scripts/sccache.sh /scripts/ RUN sh /scripts/sccache.sh -ENV SCRIPT \ - python3 ../x.py check && \ +ENV SCRIPT="python3 ../x.py check && \ python3 ../x.py clippy ci --stage 2 && \ python3 ../x.py test --stage 1 core alloc std test proc_macro && \ # Elsewhere, we run all tests for the host. A number of codegen tests are sensitive to the target pointer @@ -48,4 +47,4 @@ ENV SCRIPT \ RUSTDOCFLAGS=\"--document-private-items --document-hidden-items\" python3 ../x.py doc library/test --stage 1 && \ # The BOOTSTRAP_TRACING flag is added to verify whether the # bootstrap process compiles successfully with this flag enabled. - BOOTSTRAP_TRACING=1 python3 ../x.py --help + BOOTSTRAP_TRACING=1 python3 ../x.py --help" diff --git a/src/ci/docker/host-x86_64/tidy/Dockerfile b/src/ci/docker/host-x86_64/tidy/Dockerfile index 133192e8ac214..e84d61e0b99cc 100644 --- a/src/ci/docker/host-x86_64/tidy/Dockerfile +++ b/src/ci/docker/host-x86_64/tidy/Dockerfile @@ -39,5 +39,5 @@ COPY host-x86_64/pr-check-1/validate-toolstate.sh /scripts/ # NOTE: intentionally uses python2 for x.py so we can test it still works. # validate-toolstate only runs in our CI, so it's ok for it to only support python3. -ENV SCRIPT TIDY_PRINT_DIFF=1 python2.7 ../x.py test \ - src/tools/tidy tidyselftest --extra-checks=py,cpp,js,spellcheck +ENV SCRIPT="TIDY_PRINT_DIFF=1 python2.7 ../x.py test \ + src/tools/tidy tidyselftest --extra-checks=py,cpp,js,spellcheck" From aabb3d8fff4dd5a2e413cd981b426096900f1799 Mon Sep 17 00:00:00 2001 From: Redddy Date: Sun, 8 Mar 2026 10:56:57 +0900 Subject: [PATCH 05/25] Update query documentation to reflect QueryKey changes --- src/doc/rustc-dev-guide/src/query.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/doc/rustc-dev-guide/src/query.md b/src/doc/rustc-dev-guide/src/query.md index 5ab2ab428e811..1621d79db247a 100644 --- a/src/doc/rustc-dev-guide/src/query.md +++ b/src/doc/rustc-dev-guide/src/query.md @@ -90,7 +90,7 @@ dependencies of the local crate) Note that what determines the crate that a query is targeting is not the *kind* of query, but the *key*. For example, when you invoke `tcx.type_of(def_id)`, that could be a local query or an external query, depending on what crate the `def_id` -is referring to (see the [`self::keys::Key`][Key] trait for more information on how that works). +is referring to (see the [`self::keys::QueryKey`][QueryKey] trait for more information on how that works). Providers always have the same signature: @@ -308,7 +308,7 @@ Let's go over these elements one by one: Also used as the name of a struct (`ty::queries::type_of`) that will be generated to represent this query. - **Query key type:** the type of the argument to this query. - This type must implement the [`ty::query::keys::Key`][Key] trait, which + This type must implement the [`ty::query::keys::QueryKey`][QueryKey] trait, which defines (for example) how to map it to a crate, and so forth. - **Result type of query:** the type produced by this query. This type should (a) not use `RefCell` or other interior mutability and (b) be @@ -317,7 +317,7 @@ Let's go over these elements one by one: - **Query modifiers:** various flags and options that customize how the query is processed (mostly with respect to [incremental compilation][incrcomp]). -[Key]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/query/keys/trait.Key.html +[QueryKey]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/query/keys/trait.QueryKey.html [incrcomp]: queries/incremental-compilation-in-detail.html#query-modifiers So, to add a query: From bf4004a24a352182d784db642a8e43b8c1e05396 Mon Sep 17 00:00:00 2001 From: Redddy Date: Sun, 8 Mar 2026 10:37:47 +0900 Subject: [PATCH 06/25] Update conventions for TODO and FIXME comments --- src/doc/rustc-dev-guide/src/conventions.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/doc/rustc-dev-guide/src/conventions.md b/src/doc/rustc-dev-guide/src/conventions.md index 0e08ef9042d1e..0440fb0c5e736 100644 --- a/src/doc/rustc-dev-guide/src/conventions.md +++ b/src/doc/rustc-dev-guide/src/conventions.md @@ -139,6 +139,8 @@ if foo { } ``` +If you want to leave a note in the codebase, use `// FIXME` instead. + ## Using crates from crates.io From c15947596f521dcf3f3d90515fee2dd2e8435587 Mon Sep 17 00:00:00 2001 From: Redddy Date: Mon, 9 Mar 2026 10:11:42 +0900 Subject: [PATCH 07/25] Fix typo in feature gate check --- src/doc/rustc-dev-guide/src/feature-gate-check.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/rustc-dev-guide/src/feature-gate-check.md b/src/doc/rustc-dev-guide/src/feature-gate-check.md index 59e50837c52e2..038a14ac070e1 100644 --- a/src/doc/rustc-dev-guide/src/feature-gate-check.md +++ b/src/doc/rustc-dev-guide/src/feature-gate-check.md @@ -8,7 +8,7 @@ nightly-only `#![feature(...)]` opt-in. This chapter documents the implementation of feature gating: where gates are defined, how they are enabled, and how usage is verified. - + ## Feature Definitions From 91c3763234b547a20fa868330030f905da894a02 Mon Sep 17 00:00:00 2001 From: The rustc-josh-sync Cronjob Bot Date: Mon, 9 Mar 2026 04:46:28 +0000 Subject: [PATCH 08/25] Prepare for merging from rust-lang/rust This updates the rust-version file to eda4fc7733ee89e484d7120cafbd80dcb2fce66e. --- src/doc/rustc-dev-guide/rust-version | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/rustc-dev-guide/rust-version b/src/doc/rustc-dev-guide/rust-version index 4dedd81b00666..db9492636f6ac 100644 --- a/src/doc/rustc-dev-guide/rust-version +++ b/src/doc/rustc-dev-guide/rust-version @@ -1 +1 @@ -e7d90c695a39426baf5ae705de2f9570a72229de +eda4fc7733ee89e484d7120cafbd80dcb2fce66e From 752f75dd977b48f67d264248ad126eb816319cbe Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Mon, 9 Mar 2026 21:09:34 +0100 Subject: [PATCH 09/25] document that older LLVM versions come with increased risk --- src/doc/rustc-dev-guide/src/backend/updating-llvm.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/doc/rustc-dev-guide/src/backend/updating-llvm.md b/src/doc/rustc-dev-guide/src/backend/updating-llvm.md index 3d0e130b6aaa6..fb340342502a0 100644 --- a/src/doc/rustc-dev-guide/src/backend/updating-llvm.md +++ b/src/doc/rustc-dev-guide/src/backend/updating-llvm.md @@ -6,7 +6,10 @@ Rust supports building against multiple LLVM versions: * Tip-of-tree for the current LLVM development branch is usually supported within a few days. PRs for such fixes are tagged with `llvm-main`. * The latest released major version is always supported. -* The one or two preceding major versions are usually supported. +* The one or two preceding major versions are usually supported in the sense that they are expected + to build successfully and pass most tests. However, fixes for miscompilations often do not get + backported to past LLVM versions, so using rustc with older versions of LLVM comes with an + increased risk of soundness bugs. We strongly recommend using the latest version of LLVM. By default, Rust uses its own fork in the [rust-lang/llvm-project repository]. This fork is based on a `release/$N.x` branch of the upstream project, where From a5f88c783eb7090d3c154a58a0d260a99fef8791 Mon Sep 17 00:00:00 2001 From: Manuel Drehwald Date: Tue, 10 Mar 2026 00:48:27 -0400 Subject: [PATCH 10/25] add autodiff download instructions --- .../src/autodiff/installation.md | 49 ++++++++++++++++++- 1 file changed, 48 insertions(+), 1 deletion(-) diff --git a/src/doc/rustc-dev-guide/src/autodiff/installation.md b/src/doc/rustc-dev-guide/src/autodiff/installation.md index e05fdc1160f2f..6b66a9dcb2d5f 100644 --- a/src/doc/rustc-dev-guide/src/autodiff/installation.md +++ b/src/doc/rustc-dev-guide/src/autodiff/installation.md @@ -1,6 +1,50 @@ # Installation -In the near future, `std::autodiff` should become available in nightly builds for users. As a contributor however, you will still need to build rustc from source. Please be aware that the msvc target is not supported at the moment, all other tier 1 targets should work. Please open an issue if you encounter any problems on a supported tier 1 target, or if you successfully build this project on a tier2/tier3 target. +In the near future, `std::autodiff` should become available for users via rustup. As a rustc/enzyme/autodiff contributor however, you will still need to build rustc from source. +For the meantime, you can download up-to-date builds to enable `std::autodiff` on your latest nightly toolchain, if you are using either of: +**Linux**, with `x86_64-unknown-linux-gnu` or `aarch64-unknown-linux-gnu` +**Windows**, with `x86_64-llvm-mingw` or `aarch64-llvm-mingw` + +You can also download slightly outdated builds for **Apple** (aarch64-apple), which should generally work for now. + +If you need any other platform, you can build rustc including autodiff from source. Please open an issue if you want to help enabling automatic builds for your prefered target. + +## Installation guide + +If you want to use `std::autodiff` and don't plan to contribute PR's to the project, then we recommend to just use your existing nightly installation and download the missing component. In the future, rustup will be able to do it for you. +For now, you'll have to manually download and copy it. + +1) On our github repository, find the last merged PR: [`Repo`] +2) Scroll down to the lower end of the PR, where you'll find a rust-bors message saying `Test successful` with a `CI` link. +3) Click on the `CI` link, and grep for your target. E.g. `dist-x86_64-linux` or `dist-aarch64-llvm-mingw` and click `Load summary`. +4) Under the `CI artifacts` section, find the `enzyme-nightly` artifact, download, and unpack it. +5) Copy the artifact (libEnzyme-22.so for linux, libEnzyme-22.dylib for apple, etc.), which should be in a folder named `enzyme-preview`, to your rust toolchain directory. E.g. for linux: `cp ~/Downloads/enzyme-nightly-x86_64-unknown-linux-gnu/enzyme-preview/lib/rustlib/x86_64-unknown-linux-gnu/lib/libEnzyme-22.so ~/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib` + +Apple support was temporarily reverted, due to downstream breakages. If you want to download autodiff for apple, please look at the artifacts from this [`run`]. + +## Installation guide for Nix user. + +This setup was recommended by a nix and autodiff user. It uses [`Overlay`]. Please verify for yourself if you are comfortable using that repository. +In that case you might use the following nix configuration to get a rustc that supports `std::autodiff`. +```nix +{ + enzymeLib = pkgs.fetchzip { + url = "https://ci-artifacts.rust-lang.org/rustc-builds/ec818fda361ca216eb186f5cf45131bd9c776bb4/enzyme-nightly-x86_64-unknown-linux-gnu.tar.xz"; + sha256 = "sha256-Rnrop44vzS+qmYNaRoMNNMFyAc3YsMnwdNGYMXpZ5VY="; + }; + + rustToolchain = pkgs.symlinkJoin { + name = "rust-with-enzyme"; + paths = [pkgs.rust-bin.nightly.latest.default]; + nativeBuildInputs = [pkgs.makeWrapper]; + postBuild = '' + libdir=$out/lib/rustlib/x86_64-unknown-linux-gnu/lib + cp ${enzymeLib}/enzyme-preview/lib/rustlib/x86_64-unknown-linux-gnu/lib/libEnzyme-22.so $libdir/ + wrapProgram $out/bin/rustc --add-flags "--sysroot $out" + ''; + }; +} +``` ## Build instructions @@ -87,3 +131,6 @@ ninja ``` This will build Enzyme, and you can find it in `Enzyme/enzyme/build/lib/Enzyme.so`. (Endings might differ based on your OS). +[`Repo`]: https://github.com/rust-lang/rust/ +[`run`]: https://github.com/rust-lang/rust/pull/153026#issuecomment-3950046599 +[`Overlay`]: https://github.com/oxalica/rust-overlay From 4bd7718430143cd3bc071ed33fbfec12eac4a0f9 Mon Sep 17 00:00:00 2001 From: Redddy Date: Tue, 10 Mar 2026 16:01:31 +0900 Subject: [PATCH 11/25] Remove emoji :) --- src/doc/rustc-dev-guide/src/building/how-to-build-and-run.md | 1 - 1 file changed, 1 deletion(-) diff --git a/src/doc/rustc-dev-guide/src/building/how-to-build-and-run.md b/src/doc/rustc-dev-guide/src/building/how-to-build-and-run.md index fc8fe402bfa9e..317b7c2564cbc 100644 --- a/src/doc/rustc-dev-guide/src/building/how-to-build-and-run.md +++ b/src/doc/rustc-dev-guide/src/building/how-to-build-and-run.md @@ -110,7 +110,6 @@ Also, using `x` rather than `x.py` is recommended as: Notice that this is not absolute. For instance, using Nushell in VSCode on Win10, typing `x` or `./x` still opens `x.py` in an editor rather than invoking the program. -:) In the rest of this guide, we use `x` rather than `x.py` directly. The following command: From 9fcec027de891d48960a3965973bab1854372eb6 Mon Sep 17 00:00:00 2001 From: ralpha Date: Wed, 11 Mar 2026 13:28:59 +0100 Subject: [PATCH 12/25] unused_macro_rules switched used and unused comments --- compiler/rustc_lint_defs/src/builtin.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/compiler/rustc_lint_defs/src/builtin.rs b/compiler/rustc_lint_defs/src/builtin.rs index 38ffecbafa06b..6f7a47c36817b 100644 --- a/compiler/rustc_lint_defs/src/builtin.rs +++ b/compiler/rustc_lint_defs/src/builtin.rs @@ -1032,8 +1032,8 @@ declare_lint! { /// ```rust /// #[warn(unused_macro_rules)] /// macro_rules! unused_empty { - /// (hello) => { println!("Hello, world!") }; // This rule is unused - /// () => { println!("empty") }; // This rule is used + /// (hello) => { println!("Hello, world!") }; // This rule is used + /// () => { println!("empty") }; // This rule is unused /// } /// /// fn main() { From c909ae5a35dc6ebaae7324f16d008e4196b1936a Mon Sep 17 00:00:00 2001 From: cyrgani Date: Wed, 11 Mar 2026 18:26:49 +0000 Subject: [PATCH 13/25] add test that an incomplete feature emits a warning --- compiler/rustc_feature/src/unstable.rs | 2 ++ compiler/rustc_span/src/symbol.rs | 1 + tests/ui/feature-gates/incomplete-features.rs | 13 +++++++++++++ .../feature-gates/incomplete-features.warn.stderr | 14 ++++++++++++++ 4 files changed, 30 insertions(+) create mode 100644 tests/ui/feature-gates/incomplete-features.rs create mode 100644 tests/ui/feature-gates/incomplete-features.warn.stderr diff --git a/compiler/rustc_feature/src/unstable.rs b/compiler/rustc_feature/src/unstable.rs index 39e886227d946..ebb912ed90d0b 100644 --- a/compiler/rustc_feature/src/unstable.rs +++ b/compiler/rustc_feature/src/unstable.rs @@ -257,6 +257,8 @@ declare_features! ( (internal, rustc_attrs, "1.0.0", None), /// Allows using the `#[stable]` and `#[unstable]` attributes. (internal, staged_api, "1.0.0", None), + /// Perma-unstable, only used to test the `incomplete_features` lint. + (incomplete, test_incomplete_feature, "CURRENT_RUSTC_VERSION", None), /// Added for testing unstable lints; perma-unstable. (internal, test_unstable_lint, "1.60.0", None), /// Use for stable + negative coherence and strict coherence depending on trait's diff --git a/compiler/rustc_span/src/symbol.rs b/compiler/rustc_span/src/symbol.rs index 257ac3f51c2c1..7e4c80df3f7cf 100644 --- a/compiler/rustc_span/src/symbol.rs +++ b/compiler/rustc_span/src/symbol.rs @@ -2005,6 +2005,7 @@ symbols! { test_2018_feature, test_accepted_feature, test_case, + test_incomplete_feature, test_removed_feature, test_runner, test_unstable_lint, diff --git a/tests/ui/feature-gates/incomplete-features.rs b/tests/ui/feature-gates/incomplete-features.rs new file mode 100644 index 0000000000000..7f8f1a46ebcb0 --- /dev/null +++ b/tests/ui/feature-gates/incomplete-features.rs @@ -0,0 +1,13 @@ +//! Make sure that incomplete features emit the `incomplete_features` lint. + +// gate-test-test_incomplete_feature + +//@ check-pass +//@ revisions: warn expect + +#![cfg_attr(warn, warn(incomplete_features))] +#![cfg_attr(expect, expect(incomplete_features))] + +#![feature(test_incomplete_feature)] //[warn]~ WARN the feature `test_incomplete_feature` is incomplete + +fn main() {} diff --git a/tests/ui/feature-gates/incomplete-features.warn.stderr b/tests/ui/feature-gates/incomplete-features.warn.stderr new file mode 100644 index 0000000000000..7dda9f3648da5 --- /dev/null +++ b/tests/ui/feature-gates/incomplete-features.warn.stderr @@ -0,0 +1,14 @@ +warning: the feature `test_incomplete_feature` is incomplete and may not be safe to use and/or cause compiler crashes + --> $DIR/incomplete-features.rs:11:12 + | +LL | #![feature(test_incomplete_feature)] + | ^^^^^^^^^^^^^^^^^^^^^^^ + | +note: the lint level is defined here + --> $DIR/incomplete-features.rs:8:24 + | +LL | #![cfg_attr(warn, warn(incomplete_features))] + | ^^^^^^^^^^^^^^^^^^^ + +warning: 1 warning emitted + From db26b5b8e01a621417e08a7609f4216b6768ad43 Mon Sep 17 00:00:00 2001 From: binarycat Date: Wed, 11 Mar 2026 18:07:27 -0500 Subject: [PATCH 14/25] editorconfig: css uses tabs --- .editorconfig | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.editorconfig b/.editorconfig index 6c8560aa1f543..d2d788d2172f7 100644 --- a/.editorconfig +++ b/.editorconfig @@ -12,6 +12,9 @@ trim_trailing_whitespace = true indent_style = space indent_size = 4 +[*.css] +indent_style = tab + # some tests need trailing whitespace in output snapshots [tests/**] trim_trailing_whitespace = false From 5e305ab74dee728f17b833d620cc7832685c4804 Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Thu, 12 Mar 2026 02:05:08 +0100 Subject: [PATCH 15/25] sembr src/backend/updating-llvm.md --- src/doc/rustc-dev-guide/src/backend/updating-llvm.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/doc/rustc-dev-guide/src/backend/updating-llvm.md b/src/doc/rustc-dev-guide/src/backend/updating-llvm.md index fb340342502a0..56fa49ef2a2e4 100644 --- a/src/doc/rustc-dev-guide/src/backend/updating-llvm.md +++ b/src/doc/rustc-dev-guide/src/backend/updating-llvm.md @@ -7,9 +7,11 @@ Rust supports building against multiple LLVM versions: PRs for such fixes are tagged with `llvm-main`. * The latest released major version is always supported. * The one or two preceding major versions are usually supported in the sense that they are expected - to build successfully and pass most tests. However, fixes for miscompilations often do not get + to build successfully and pass most tests. + However, fixes for miscompilations often do not get backported to past LLVM versions, so using rustc with older versions of LLVM comes with an - increased risk of soundness bugs. We strongly recommend using the latest version of LLVM. + increased risk of soundness bugs. + We strongly recommend using the latest version of LLVM. By default, Rust uses its own fork in the [rust-lang/llvm-project repository]. This fork is based on a `release/$N.x` branch of the upstream project, where From 5de87cd04af71d5f8893f14f88a2baf8358cacef Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Thu, 12 Mar 2026 02:08:20 +0100 Subject: [PATCH 16/25] sembr src/diagnostics/translation.md --- src/doc/rustc-dev-guide/src/diagnostics/translation.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/doc/rustc-dev-guide/src/diagnostics/translation.md b/src/doc/rustc-dev-guide/src/diagnostics/translation.md index cf95727e2a673..a22ede5e9c3ba 100644 --- a/src/doc/rustc-dev-guide/src/diagnostics/translation.md +++ b/src/doc/rustc-dev-guide/src/diagnostics/translation.md @@ -31,8 +31,7 @@ There are two ways of writing translatable diagnostics: ("Simple" diagnostics being those that don't require a lot of logic in deciding to emit subdiagnostics and can therefore be represented as diagnostic structs). See [the diagnostic and subdiagnostic structs documentation](./diagnostic-structs.md). -2. Using typed identifiers with `Diag` APIs (in - `Diagnostic` or `Subdiagnostic` implementations). +2. Using typed identifiers with `Diag` APIs (in `Diagnostic` or `Subdiagnostic` implementations). When adding or changing a translatable diagnostic, you don't need to worry about the translations. From 7963b55d9a163103f60b67dd7db453f9a39fc24e Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Thu, 12 Mar 2026 02:09:02 +0100 Subject: [PATCH 17/25] sembr src/git.md --- src/doc/rustc-dev-guide/src/git.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/doc/rustc-dev-guide/src/git.md b/src/doc/rustc-dev-guide/src/git.md index 34e419fa52259..faa2d8f2a3a21 100644 --- a/src/doc/rustc-dev-guide/src/git.md +++ b/src/doc/rustc-dev-guide/src/git.md @@ -383,7 +383,9 @@ Both the upside and downside of this is that it simplifies the history. On the one hand, you lose track of the steps in which changes were made, but the history becomes easier to work with. -The easiest way to squash your commits in a PR on the `rust-lang/rust` repository is to use the `@bors squash` command in a comment on the PR. By default, [bors] combines all commit messages of the PR into the squashed commit message. To customize the commit message, use `@bors squash msg=`. +The easiest way to squash your commits in a PR on the `rust-lang/rust` repository is to use the `@bors squash` command in a comment on the PR. +By default, [bors] combines all commit messages of the PR into the squashed commit message. +To customize the commit message, use `@bors squash msg=`. If you want to squash commits using local git operations, read on below. From 751562faf55a0734d27ebb17281926338b632829 Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Thu, 12 Mar 2026 02:10:03 +0100 Subject: [PATCH 18/25] sembr src/tracing.md --- src/doc/rustc-dev-guide/src/tracing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/doc/rustc-dev-guide/src/tracing.md b/src/doc/rustc-dev-guide/src/tracing.md index 151670d089970..78a0fe4af2ff2 100644 --- a/src/doc/rustc-dev-guide/src/tracing.md +++ b/src/doc/rustc-dev-guide/src/tracing.md @@ -14,8 +14,8 @@ of `tracing-subscriber`](https://docs.rs/tracing-subscriber/0.2.24/tracing_subsc ## Environment variables -This is an overview of the environment variables rustc accepts to customize -its tracing output. The definition of these can mostly be found in `compiler/rustc_log/src/lib.rs`. +This is an overview of the environment variables rustc accepts to customize its tracing output. +The definition of these can mostly be found in `compiler/rustc_log/src/lib.rs`. | Name | Usage | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------- | From cfcbcb715c5120e481b2d1303b590a5eb2417e55 Mon Sep 17 00:00:00 2001 From: Tony Kan Date: Wed, 11 Mar 2026 15:10:45 -0700 Subject: [PATCH 19/25] fix(query): Pass query key to value_from_cycle_error Co-authored-by: Daria Sukhonina Co-authored-by: Nicholas Nethercote --- compiler/rustc_middle/src/query/plumbing.rs | 8 ++++-- compiler/rustc_query_impl/src/execution.rs | 12 +++++---- .../rustc_query_impl/src/from_cycle_error.rs | 25 ++++++++----------- compiler/rustc_query_impl/src/plumbing.rs | 2 +- 4 files changed, 25 insertions(+), 22 deletions(-) diff --git a/compiler/rustc_middle/src/query/plumbing.rs b/compiler/rustc_middle/src/query/plumbing.rs index 72330eab30d58..33c38adcef058 100644 --- a/compiler/rustc_middle/src/query/plumbing.rs +++ b/compiler/rustc_middle/src/query/plumbing.rs @@ -136,8 +136,12 @@ pub struct QueryVTable<'tcx, C: QueryCache> { /// For `no_hash` queries, this function pointer is None. pub hash_value_fn: Option, &C::Value) -> Fingerprint>, - pub value_from_cycle_error: - fn(tcx: TyCtxt<'tcx>, cycle_error: CycleError, guar: ErrorGuaranteed) -> C::Value, + pub value_from_cycle_error: fn( + tcx: TyCtxt<'tcx>, + key: C::Key, + cycle_error: CycleError, + guar: ErrorGuaranteed, + ) -> C::Value, pub format_value: fn(&C::Value) -> String, /// Formats a human-readable description of this query and its key, as diff --git a/compiler/rustc_query_impl/src/execution.rs b/compiler/rustc_query_impl/src/execution.rs index a892958d6a810..d8dc004f1cf7a 100644 --- a/compiler/rustc_query_impl/src/execution.rs +++ b/compiler/rustc_query_impl/src/execution.rs @@ -125,17 +125,18 @@ where fn mk_cycle<'tcx, C: QueryCache>( query: &'tcx QueryVTable<'tcx, C>, tcx: TyCtxt<'tcx>, + key: C::Key, cycle_error: CycleError, ) -> C::Value { let error = report_cycle(tcx.sess, &cycle_error); match query.cycle_error_handling { CycleErrorHandling::Error => { let guar = error.emit(); - (query.value_from_cycle_error)(tcx, cycle_error, guar) + (query.value_from_cycle_error)(tcx, key, cycle_error, guar) } CycleErrorHandling::DelayBug => { let guar = error.delay_as_bug(); - (query.value_from_cycle_error)(tcx, cycle_error, guar) + (query.value_from_cycle_error)(tcx, key, cycle_error, guar) } } } @@ -219,6 +220,7 @@ where fn cycle_error<'tcx, C: QueryCache>( query: &'tcx QueryVTable<'tcx, C>, tcx: TyCtxt<'tcx>, + key: C::Key, try_execute: QueryJobId, span: Span, ) -> (C::Value, Option) { @@ -229,7 +231,7 @@ fn cycle_error<'tcx, C: QueryCache>( .expect("failed to collect active queries"); let error = find_cycle_in_stack(try_execute, job_map, ¤t_query_job(), span); - (mk_cycle(query, tcx, error.lift()), None) + (mk_cycle(query, tcx, key, error.lift()), None) } #[inline(always)] @@ -274,7 +276,7 @@ fn wait_for_query<'tcx, C: QueryCache>( (v, Some(index)) } - Err(cycle) => (mk_cycle(query, tcx, cycle.lift()), None), + Err(cycle) => (mk_cycle(query, tcx, key, cycle.lift()), None), } } @@ -337,7 +339,7 @@ fn try_execute_query<'tcx, C: QueryCache, const INCR: bool>( // If we are single-threaded we know that we have cycle error, // so we just return the error. - cycle_error(query, tcx, id, span) + cycle_error(query, tcx, key, id, span) } } ActiveKeyStatus::Poisoned => FatalError.raise(), diff --git a/compiler/rustc_query_impl/src/from_cycle_error.rs b/compiler/rustc_query_impl/src/from_cycle_error.rs index 0b7f69765823f..c69d3eb9a0f05 100644 --- a/compiler/rustc_query_impl/src/from_cycle_error.rs +++ b/compiler/rustc_query_impl/src/from_cycle_error.rs @@ -15,34 +15,34 @@ use rustc_middle::query::erase::erase_val; use rustc_middle::ty::layout::{LayoutError, TyAndLayout}; use rustc_middle::ty::{self, Ty, TyCtxt}; use rustc_middle::{bug, span_bug}; -use rustc_span::def_id::LocalDefId; +use rustc_span::def_id::{DefId, LocalDefId}; use rustc_span::{ErrorGuaranteed, Span}; use crate::job::report_cycle; pub(crate) fn specialize_query_vtables<'tcx>(vtables: &mut QueryVTables<'tcx>) { vtables.type_of.value_from_cycle_error = - |tcx, _, guar| erase_val(ty::EarlyBinder::bind(Ty::new_error(tcx, guar))); + |tcx, _, _, guar| erase_val(ty::EarlyBinder::bind(Ty::new_error(tcx, guar))); vtables.type_of_opaque_hir_typeck.value_from_cycle_error = - |tcx, _, guar| erase_val(ty::EarlyBinder::bind(Ty::new_error(tcx, guar))); + |tcx, _, _, guar| erase_val(ty::EarlyBinder::bind(Ty::new_error(tcx, guar))); vtables.erase_and_anonymize_regions_ty.value_from_cycle_error = - |tcx, _, guar| erase_val(Ty::new_error(tcx, guar)); + |tcx, _, _, guar| erase_val(Ty::new_error(tcx, guar)); - vtables.fn_sig.value_from_cycle_error = |tcx, cycle, guar| erase_val(fn_sig(tcx, cycle, guar)); + vtables.fn_sig.value_from_cycle_error = |tcx, key, _, guar| erase_val(fn_sig(tcx, key, guar)); vtables.check_representability.value_from_cycle_error = - |tcx, cycle, guar| check_representability(tcx, cycle, guar); + |tcx, _, cycle, guar| check_representability(tcx, cycle, guar); vtables.check_representability_adt_ty.value_from_cycle_error = - |tcx, cycle, guar| check_representability(tcx, cycle, guar); + |tcx, _, cycle, guar| check_representability(tcx, cycle, guar); vtables.variances_of.value_from_cycle_error = - |tcx, cycle, guar| erase_val(variances_of(tcx, cycle, guar)); + |tcx, _, cycle, guar| erase_val(variances_of(tcx, cycle, guar)); vtables.layout_of.value_from_cycle_error = - |tcx, cycle, guar| erase_val(layout_of(tcx, cycle, guar)); + |tcx, _, cycle, guar| erase_val(layout_of(tcx, cycle, guar)); } pub(crate) fn default<'tcx>(tcx: TyCtxt<'tcx>, cycle_error: CycleError, query_name: &str) -> ! { @@ -57,15 +57,12 @@ pub(crate) fn default<'tcx>(tcx: TyCtxt<'tcx>, cycle_error: CycleError, query_na fn fn_sig<'tcx>( tcx: TyCtxt<'tcx>, - cycle_error: CycleError, + def_id: DefId, guar: ErrorGuaranteed, ) -> ty::EarlyBinder<'tcx, ty::PolyFnSig<'tcx>> { let err = Ty::new_error(tcx, guar); - let arity = if let Some(info) = cycle_error.cycle.get(0) - && info.frame.dep_kind == DepKind::fn_sig - && let Some(def_id) = info.frame.def_id - && let Some(node) = tcx.hir_get_if_local(def_id) + let arity = if let Some(node) = tcx.hir_get_if_local(def_id) && let Some(sig) = node.fn_sig() { sig.decl.inputs.len() diff --git a/compiler/rustc_query_impl/src/plumbing.rs b/compiler/rustc_query_impl/src/plumbing.rs index ddce892345907..78d5fd3de1f00 100644 --- a/compiler/rustc_query_impl/src/plumbing.rs +++ b/compiler/rustc_query_impl/src/plumbing.rs @@ -487,7 +487,7 @@ macro_rules! define_queries { #[cfg(not($cache_on_disk))] is_loadable_from_disk_fn: |_tcx, _key, _index| false, - value_from_cycle_error: |tcx, cycle, _| { + value_from_cycle_error: |tcx, _, cycle, _| { $crate::from_cycle_error::default(tcx, cycle, stringify!($name)) }, From 3464048bc49281f0f947178081f4d41993d253e1 Mon Sep 17 00:00:00 2001 From: Tony Kan Date: Wed, 11 Mar 2026 15:10:55 -0700 Subject: [PATCH 20/25] test(parallel): Add regression test for #153391 Co-authored-by: Daria Sukhonina --- .../parallel-rustc/fn-sig-cycle-ice-153391.rs | 18 +++++++++++ .../fn-sig-cycle-ice-153391.stderr | 31 +++++++++++++++++++ 2 files changed, 49 insertions(+) create mode 100644 tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.rs create mode 100644 tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.stderr diff --git a/tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.rs b/tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.rs new file mode 100644 index 0000000000000..0108ada8c08c3 --- /dev/null +++ b/tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.rs @@ -0,0 +1,18 @@ +// Regression test for #153391. +// +//@ edition:2024 +//@ compile-flags: -Z threads=16 +//@ compare-output-by-lines +//@ ignore-test (#142063) + +trait A { + fn g() -> B; + //~^ ERROR expected a type, found a trait +} + +trait B { + fn bar(&self, x: &A); + //~^ ERROR expected a type, found a trait +} + +fn main() {} diff --git a/tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.stderr b/tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.stderr new file mode 100644 index 0000000000000..4d348cf22f4ef --- /dev/null +++ b/tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.stderr @@ -0,0 +1,31 @@ +error[E0782]: expected a type, found a trait + --> $DIR/fn-sig-cycle-ice-153391.rs:8:15 + | +LL | fn g() -> B; + | ^ + | +help: `B` is dyn-incompatible, use `impl B` to return an opaque type, as long as you return a single underlying type + | +LL | fn g() -> impl B; + | ++++ + +error[E0782]: expected a type, found a trait + --> $DIR/fn-sig-cycle-ice-153391.rs:13:23 + | +LL | fn bar(&self, x: &A); + | ^ + | + = note: `A` is dyn-incompatible, otherwise a trait object could be used +help: use a new generic type parameter, constrained by `A` + | +LL - fn bar(&self, x: &A); +LL + fn bar(&self, x: &T); + | +help: you can also use an opaque type, but users won't be able to specify the type parameter when calling the `fn`, having to rely exclusively on type inference + | +LL | fn bar(&self, x: &impl A); + | ++++ + +error: aborting due to 2 previous errors + +For more information about this error, try `rustc --explain E0782`. From ac062fd2238552eaddfd429e71bff14c066c5ea2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Ber=C3=A1nek?= Date: Wed, 11 Mar 2026 17:20:41 +0100 Subject: [PATCH 21/25] Allow auto jobs to be non-blocking --- src/ci/citool/src/jobs.rs | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/ci/citool/src/jobs.rs b/src/ci/citool/src/jobs.rs index 245ab31fa6446..cc93761e9604e 100644 --- a/src/ci/citool/src/jobs.rs +++ b/src/ci/citool/src/jobs.rs @@ -200,12 +200,14 @@ fn validate_job_database(db: &JobDatabase) -> anyhow::Result<()> { equivalent_modulo_carve_out(pr_job, auto_job)?; } - // Auto CI jobs must all "fail-fast" to avoid wasting Auto CI resources. For instance, `tidy`. + // Auto CI should "fail-fast" to avoid wasting Auto CI resources. + // However, some experimental auto jobs can be made optional, for example if we are unsure about + // their flakiness. Those have to be prefixed with `optional-`. for auto_job in &db.auto_jobs { - if auto_job.continue_on_error == Some(true) { + if auto_job.continue_on_error == Some(true) && !auto_job.name.starts_with("optional-") { return Err(anyhow!( - "Auto job `{}` cannot have `continue_on_error: true`", - auto_job.name + "Auto job `{job}` cannot have `continue_on_error: true`. If the job should be optional, name it `optional-{job}`.", + job = auto_job.name )); } } From 96e4833bead3217951fcd4604a3b1a3a92b59059 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Ber=C3=A1nek?= Date: Thu, 12 Mar 2026 09:07:02 +0100 Subject: [PATCH 22/25] Add new CI job that runs tests with a toolchain built with multiple threads --- .../Dockerfile | 36 +++++++++++++++++++ src/ci/github-actions/jobs.yml | 5 +++ 2 files changed, 41 insertions(+) create mode 100644 src/ci/docker/host-x86_64/optional-x86_64-gnu-parallel-frontend/Dockerfile diff --git a/src/ci/docker/host-x86_64/optional-x86_64-gnu-parallel-frontend/Dockerfile b/src/ci/docker/host-x86_64/optional-x86_64-gnu-parallel-frontend/Dockerfile new file mode 100644 index 0000000000000..8f7c7ebe35559 --- /dev/null +++ b/src/ci/docker/host-x86_64/optional-x86_64-gnu-parallel-frontend/Dockerfile @@ -0,0 +1,36 @@ +FROM ubuntu:22.04 + +ARG DEBIAN_FRONTEND=noninteractive +RUN apt-get update && apt-get install -y --no-install-recommends \ + g++ \ + make \ + ninja-build \ + file \ + curl \ + ca-certificates \ + python3 \ + git \ + cmake \ + sudo \ + gdb \ + libssl-dev \ + pkg-config \ + xz-utils \ + mingw-w64 \ + zlib1g-dev \ + libzstd-dev \ + && rm -rf /var/lib/apt/lists/* + +COPY scripts/sccache.sh /scripts/ +RUN sh /scripts/sccache.sh + +ENV RUST_CONFIGURE_ARGS \ + --build=x86_64-unknown-linux-gnu \ + --enable-sanitizers \ + --enable-profiler \ + --enable-compiler-docs \ + --set llvm.libzstd=true + +# Build the toolchain with multiple parallel frontend threads and then run tests +# Tests are still compiled serially at the moment (intended to be changed in follow-ups). +ENV SCRIPT python3 ../x.py --stage 2 test --set rust.parallel-frontend-threads=4 diff --git a/src/ci/github-actions/jobs.yml b/src/ci/github-actions/jobs.yml index 0687d142a3504..563083cd450bc 100644 --- a/src/ci/github-actions/jobs.yml +++ b/src/ci/github-actions/jobs.yml @@ -348,6 +348,11 @@ auto: - name: x86_64-gnu <<: *job-linux-4c + - name: optional-x86_64-gnu-parallel-frontend + # This test can be flaky, so do not cancel CI if it fails, for now. + continue_on_error: true + <<: *job-linux-4c + - name: x86_64-gnu-gcc doc_url: https://rustc-dev-guide.rust-lang.org/tests/codegen-backend-tests/cg_gcc.html <<: *job-linux-4c From b3333b3aafbc572009f3ca5f3e183ac82bd9218c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Ber=C3=A1nek?= Date: Thu, 12 Mar 2026 09:35:56 +0100 Subject: [PATCH 23/25] Document optional auto jobs in the rustc-dev-guide --- src/doc/rustc-dev-guide/src/tests/ci.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/doc/rustc-dev-guide/src/tests/ci.md b/src/doc/rustc-dev-guide/src/tests/ci.md index 6b63f68b29ee9..5161194492e6c 100644 --- a/src/doc/rustc-dev-guide/src/tests/ci.md +++ b/src/doc/rustc-dev-guide/src/tests/ci.md @@ -109,6 +109,12 @@ The live results can be seen on [the GitHub Actions workflows page]. At any given time, at most a single `auto` build is being executed. Find out more in [Merging PRs serially with bors](#merging-prs-serially-with-bors). +Normally, when an auto job fails, the whole CI workflow immediately ends. However, it can be useful to +create auto jobs that are "non-blocking", or optional, to test them on CI for some time before blocking +merges on them. This can be useful if those jobs can be flaky. + +To do that, prefix such a job with `optional-`, and set `continue_on_error: true` for it in [`jobs.yml`]. + [platform tiers]: https://forge.rust-lang.org/release/platform-support.html#rust-platform-support [auto]: https://github.com/rust-lang/rust/tree/automation/bors/auto From 687d7dbc23753f3d6eca80cccd57dc3432325a8b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jana=20D=C3=B6nszelmann?= Date: Thu, 12 Mar 2026 09:36:46 +0100 Subject: [PATCH 24/25] actually make the is-fn test test what it says it tests --- tests/ui/async-await/async-closures/is-fn.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/ui/async-await/async-closures/is-fn.rs b/tests/ui/async-await/async-closures/is-fn.rs index 45c2b6ae342b6..1d546cd44b496 100644 --- a/tests/ui/async-await/async-closures/is-fn.rs +++ b/tests/ui/async-await/async-closures/is-fn.rs @@ -9,11 +9,11 @@ use std::future::Future; extern crate block_on; -// Check that closures that don't capture any state may implement `Fn`. +// Check that async closures that don't capture any state may implement `Fn`. fn main() { block_on::block_on(async { - async fn call_once(x: impl FnOnce(&'static str) -> F) -> F::Output { + async fn call_once(x: impl Fn(&'static str) -> F) -> F::Output { x("hello, world").await } call_once(async |x: &'static str| { From 06704919507893e4e26a3fc0adf5aefaf0356199 Mon Sep 17 00:00:00 2001 From: Nikita Popov Date: Thu, 12 Mar 2026 03:52:53 -0500 Subject: [PATCH 25/25] Don't add empty target features for target-cpu=native on macOS LLVM does not support host feature detection (only host cpu detection) on apple platforms. As such, the returned feature string will be empty. Adding this empty string to the target-features attribute results in a verifier error on LLVM 22. Fix this by not adding the empty string to the target features. The reason why this was not caught by the target-cpu-native test is that it requires a function that adds *some* target features, otherwise the attribute is omitted entirely. We achieve this with a somewhat peculiar construction that enables `neon` if it's already enabled. (This is to avoid enabling it on softfloat targets.) --- compiler/rustc_codegen_llvm/src/llvm_util.rs | 4 +++- tests/run-make/target-cpu-native/foo.rs | 8 ++++++++ tests/run-make/target-cpu-native/rmake.rs | 7 ++++++- 3 files changed, 17 insertions(+), 2 deletions(-) diff --git a/compiler/rustc_codegen_llvm/src/llvm_util.rs b/compiler/rustc_codegen_llvm/src/llvm_util.rs index fbb582fe86018..85b515f2ef9cb 100644 --- a/compiler/rustc_codegen_llvm/src/llvm_util.rs +++ b/compiler/rustc_codegen_llvm/src/llvm_util.rs @@ -702,7 +702,9 @@ pub(crate) fn global_llvm_features(sess: &Session, only_base_features: bool) -> features_string }; - features.extend(features_string.split(',').map(String::from)); + if !features_string.is_empty() { + features.extend(features_string.split(',').map(String::from)); + } } Some(_) | None => {} }; diff --git a/tests/run-make/target-cpu-native/foo.rs b/tests/run-make/target-cpu-native/foo.rs index f328e4d9d04c3..5abcd25abc3f3 100644 --- a/tests/run-make/target-cpu-native/foo.rs +++ b/tests/run-make/target-cpu-native/foo.rs @@ -1 +1,9 @@ fn main() {} + +// This forces explicit emission of a +neon target feature on targets +// where it is implied by the target-cpu, like aarch64-apple-darwin. +// This is a regression test for #153397. +#[cfg(target_feature = "neon")] +#[target_feature(enable = "neon")] +#[unsafe(no_mangle)] +pub fn with_neon() {} diff --git a/tests/run-make/target-cpu-native/rmake.rs b/tests/run-make/target-cpu-native/rmake.rs index 7b7974f309789..5791bf01bba2b 100644 --- a/tests/run-make/target-cpu-native/rmake.rs +++ b/tests/run-make/target-cpu-native/rmake.rs @@ -8,7 +8,12 @@ use run_make_support::{run, rustc}; fn main() { - let out = rustc().input("foo.rs").arg("-Ctarget-cpu=native").run().stderr_utf8(); + let out = rustc() + .input("foo.rs") + .arg("-Ctarget-cpu=native") + .arg("-Zverify-llvm-ir") + .run() + .stderr_utf8(); run("foo"); // There should be zero warnings emitted - the bug would cause "unknown CPU `native`" // to be printed out.