Skip to content

Rollup of 15 pull requests - #166105

Closed
JonathanBrouwer wants to merge 37 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-I09B4vJ
Closed

JonathanBrouwer wants to merge 37 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-I09B4vJ

Conversation

@JonathanBrouwer

@JonathanBrouwer JonathanBrouwer commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

Dnreikronos and others added 30 commits September 12, 2026 14:57
Async closure bodies are checked as coroutines, but their expected return
type was lost before body checking. Reuse the matching coroutine signature.

Keep this path limited to async closures because gen closures have a
different input shape.
Previously, Rust did not explicitly enable a PTX version target-feature,
because LLVM implied one from the selected CPU.

Starting with LLVM 22, the NVPTX backend still infers the minimum required
PTX version from the selected CPU when none is selected explicitly, but no
longer reflects that version in the enabled subtarget features. As a result,
cfg could miss the PTX version of the emitted PTX. Also, if a PTX version
below the required minimum is selected explicitly, LLVM errors.

We missed this because the corresponding NVPTX target-feature test was
mistakenly disabled.

To keep cfg evaluation consistent and avoid LLVM errors, always select an
explicit PTX version: whichever is higher between
 - Rust's minimum required PTX version, and
 - the CPU's minimum required PTX version.

Re-enable the NVPTX target-feature test and adapt it to Rust's minimum
required PTX and sm versions.

Forbid PTX and sm versions below Rust's minimum required versions by marking
the corresponding target-features as `InternalOnly`.

Add PTX and sm versions present in LLVM 22 or 23 but missing as Rust
target-features.
This doesn't affect off-chip unwinding and backtraces, but makes leaf
functions smaller and hence improves performance.

My sample program went from 40924 to 40864 bytes (-0.15%), but probe-rs
could still print a backtrace starting in a leaf function.
It was relying on the "mov r7, sp" store of the frame pointer, which we
now don't have for leaf functions.
With `-Znext-solver=globally`, the examples in the reported issue used
to ICE with "failed to resolve instance" during monomorphization.
They now fail with a normal error instead. The first example was
fixed by an earlier compiler change.

`recursion-issue-164253-1.rs` is the example from the issue
description. It should fail with "reached the recursion limit while
instantiating".

`recursion-issue-164253-2.rs` is a smaller example posted in a comment
on the issue. It should fail with E0275 ("overflow evaluating the
requirement").

Both tests run with the current and the next solver. They are
`build-fail` because the ICE happened during monomorphization, and use
`forbid-output: internal compiler error` so that the ICE cannot come
back unnoticed. `recursion_depth_exceeding_limit` is allowed because it
is unrelated to this issue and is planned to become an error.
We have four MIPS-like arches, not just the two.
…ted`

All other architecture families currently use a single macro for both
32- and 64-bit versions. Do the same for MIPS.
…graph-index, r=davidtwco

Compact the previous dependency-node reverse index

## Summary

On main, we store each dependency node’s key fingerprint twice: once in the node array and again in the reverse index. This PR instead stores _only_ node indices in the reverse index, then reads fingerprints from the node array when comparing entries.

For warm `cargo check` invocations in uv and Ruff, this reduced peak RSS by between 2.46% and 3.94% with a ~0.50% increase in instruction counts.
…gross35

Add an optional `llvm = ` argument to rustc_intrinsic.

This is meant for usage in core::arch, to define the platform-specific LLVM intrinsics that correspond to each intrinsic.

~LLM usage: I used an LLM to point me at places in the code from which to start the implementation, but I did not generate any code. The main non-trivial input from the LLM was to prevent inlining of callees annotated with rustc_llvm_intrinsic.~ Code has been since re-designed following @bjorn3's and @RalfJung's proposals so there's no trace of any LLM input left :-)

r? RalfJ
std: Combine `is_mips64_feature_detected` into `is_mips_feature_detected` and enable on MIPS release 6

All other architecture families currently use a single macro for both
32- and 64-bit versions. Do the same for MIPS.

Tracking issue: rust-lang#111188
…r=bjorn3

Check type alignment is <= type size in data layout parser

Rust requires that types have an alignment that is <= their size, so this PR checks this is the case in the data layout parser. As `i1_align` and `i8_align` must always have an alignment of 1, I've also removed those two fields from `TargetDataLayout` in the second commit and replaced any uses with `Align::ONE`.
…-attr, r=petrochenkov

Combine the spans of generic arguments without dropping `->`

Follow-up on rust-lang#165047.

As mentioned in this [comment](https://github.com/rust-lang/rust/pull/165047/changes#issuecomment-6728245944), the generic arguments' spans are being constructed without taking `->` (`Token::RArrow`) into account.
This is problematic when `->` comes from a different context (e.g., a macro).

This patch chains the entire generic argument, contributing to rust-lang#126763.

r? @petrochenkov
rustc: avoid path dependent queries in source presence checks

debugger visualizer lookups executed a query to `used_crate_source` as an rlib or rmeta spot check, creating a path dependent fingerprint that would invalidate CGUs if the artifacts were moved to different canonical paths. (frequently occurring during sandboxed build runs)

Instead, we return bitflags describing the presence of source fields from a `CrateSource` and update other relevant callers of `used_crate_source` to instead consume `CrateSourceFlags`.

r? @petrochenkov
… r=davidtwco

Adapt NVPTX target-feature handling for LLVM 22 and 23

Previously, we did not explicitly enable a PTX version target-feature, because LLVM implied one from the selected CPU.

Starting with LLVM 22, the NVPTX backend still infers the minimum required PTX version from the selected CPU when none is selected explicitly, but no longer reflects that version in the enabled subtarget features. As a result, cfg could miss the PTX version of the emitted PTX. Also, if a PTX version below the required minimum is selected explicitly, LLVM errors.
We missed this because the corresponding NVPTX target-feature test was mistakenly disabled.

With this patch we always select a PTX version explicitly, whichever is higher between
 - Rust's minimum required PTX version, and
 - the CPU's minimum required PTX version.

The patch also re-enables the NVPTX target-feature test to catch such changes in the future.
It additionally forbids PTX and sm versions below Rust's minimum required versions by marking the corresponding target-features as `InternalOnly`.
Lastly it adds PTX and sm versions present in LLVM 22 or LLVM 23 but missing as Rust target-features.

This will not prevent all issues. In fact, the following combinations might still miscompile:
```
-Ctarget-cpu=sm_101 -Ctarget-feature=+ptx90 // sm_101 was renamed starting with ptx90
-Ctarget-cpu=sm_70 -Ctarget-feature=+sm_80,+ptx81 // .target directive is sm_70 but instructions are selected from sm_80
```

cc: @kjetilkjeka
r? @ZuseZ4
@rustbot label +O-NVPTX
…re_output_diagnostic, r=davidtwco

hir_typeck: Propagate async closure output into its body

Fixes rust-lang#161619

Rustc already knows the output type it expects from an async closure, but that type wasn't reaching the closure body during type checking. When the body returned the wrong thing, rustc compared the generated async types and suggested pinning. That sends you in completely the wrong direction.

The fix carries the coroutine signature into the body check, so the regular type error points at `String::new()` and says it expected `()`.

My first pass matched any coroutine with the same def id. It looked fine, then the iterator suite caught the problem: `iter!` comes through the same path but its body has no resume input. I narrowed the match to async closure bodies. I prefer that version because it uses type information rustc already has and leaves the gen path alone. The test runs with both trait solvers, and the existing iterator tests cover the case that bit me.
…avidtwco

lint: keep type-changing casts in `raw_borrows_via_references`

Fixes rust-lang#164144

### about this bug

`raw_borrows_via_references` rewrites `&mut x as *mut usize` to `&raw mut x`.

When `x` is `[usize; 2]`, that drops the cast, so `p` becomes `*mut [usize; 2]` and the fixed code does not compile.

A cast that only changes mutability, `&mut x as *const i32`, is dropped the *same* way.

### after this fix

- Remove `as *const T` only when `&raw` already has that type.
- Otherwise suggest `&raw mut x as *mut usize`.
- A redundant cast such as `&(*x).0 as *const i32` is still removed.

### llm disclosure

The LLM (specifically, Grok 4.7) was used for improving the ui test case edge case coverage only.
…idtwco

Add regression tests for rust-lang#164253

Closes rust-lang#164253

This adds regression tests for the two examples in rust-lang#164253. Both used to ICE with `-Znext-solver=globally` ("failed to resolve instance"). They no longer ICE on current nightly, so the issue can be closed once these tests are in, as suggested in the issue.
…hanBrouwer

Prune un/under used methods of `ast::Attribute`

Many of these functions, like `Attribute::path` were mostly dead code.

There are more that are underused (basically only used by clippy), but I plan on changing clippy's attribute handling more comprehensively so I did not touch them.
[PAC] Disable rust-tail-cc for pauthtest

Fixed on mainline LLVM (but still miscompiles up until and including 23.1).

`lotsa_apples` is `extern "tail"` (LLVM `tailcc`), so the callee pops its own stack arguments. `CrateOf` is passed by value on the stack (128 bytes). pauthtest enables `ptrauth-returns`: the prologue signs LR with `pacibsp`, using the SP at function entry as the modifier. The epilogue releases the callee-popped argument area (`add sp, sp, #0x80`) *before* authenticating LR (`retab`), so authentication uses SP = entry SP + 128 and always fails.

r? @davidtwco
…laumeGomez

Move doc attribute and doc comment target checking to attribute parsing

Perhaps r? @GuillaumeGomez

Part of rust-lang#149865
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Nov 17, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors r+ p=5 force

Trying commonly failed jobs
@bors try jobs=dist-various-1,dist-various-2,test-various,test-x86_64-gnu-aux,test-x86_64-msvc-1,test-aarch64-apple-1,test-aarch64-apple-2,test-x86_64-mingw-1,test-i686-msvc,test-armhf-gnu,test-x86_64-gnu-llvm-22-3,test-aarch64-msvc-2

@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-clippy Relevant to the Clippy team. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. labels Nov 17, 2026
@rust-bors

rust-bors Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 820fcd8 has been approved by JonathanBrouwer

It is now in the queue for this repository.

@rust-bors rust-bors Bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Nov 17, 2026
@rust-bors

rust-bors Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

⌛ Trying commit 820fcd8 with merge 942fea2…

To cancel the try build, run the command @bors try cancel.

Workflow: https://github.com/rust-lang/rust/actions/runs/44110646090

rust-bors Bot pushed a commit that referenced this pull request Nov 17, 2026
Rollup of 15 pull requests


try-job: dist-various-1
try-job: dist-various-2
try-job: test-various
try-job: test-x86_64-gnu-aux
try-job: test-x86_64-msvc-1
try-job: test-aarch64-apple-1
try-job: test-aarch64-apple-2
try-job: test-x86_64-mingw-1
try-job: test-i686-msvc
try-job: test-armhf-gnu
try-job: test-x86_64-gnu-llvm-22-3
try-job: test-aarch64-msvc-2
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

The job test-x86_64-gnu-aux failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)
   Compiling rustc_crate_store v0.0.0 (/checkout/compiler/rustc_crate_store)
error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:676:15
    |
676 |     ("sm_20", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:677:15
    |
677 |     ("sm_21", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:678:15
    |
678 |     ("sm_30", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:679:15
    |
679 |     ("sm_32", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:680:15
    |
680 |     ("sm_35", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:681:15
    |
681 |     ("sm_37", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:682:15
    |
682 |     ("sm_50", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:683:15
    |
683 |     ("sm_52", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:684:15
    |
684 |     ("sm_53", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:685:15
    |
685 |     ("sm_60", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:686:15
    |
686 |     ("sm_61", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:687:15
    |
687 |     ("sm_62", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:723:15
    |
723 |     ("ptx32", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:724:15
    |
724 |     ("ptx40", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:725:15
    |
725 |     ("ptx41", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:726:15
    |
726 |     ("ptx42", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:727:15
    |
727 |     ("ptx43", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:728:15
    |
728 |     ("ptx50", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:729:15
    |
729 |     ("ptx60", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:730:15
    |
730 |     ("ptx61", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:731:15
    |
731 |     ("ptx62", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:732:15
    |
732 |     ("ptx63", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:733:15
    |
733 |     ("ptx64", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:734:15
    |
734 |     ("ptx65", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

For more information about this error, try `rustc --explain E0063`.
[RUSTC-TIMING] rustc_target test:false 2.463
error: could not compile `rustc_target` (lib) due to 24 previous errors
---
Currently active steps:
compile::Assemble { target_compiler: Compiler { stage: 1, host: x86_64-unknown-linux-gnu, forced_compiler: false } } at src/bootstrap/src/core/build_steps/tool.rs:375
compile::Rustc { target: x86_64-unknown-linux-gnu, build_compiler: Compiler { stage: 0, host: x86_64-unknown-linux-gnu, forced_compiler: false }, crates: [] } at src/bootstrap/src/core/build_steps/compile.rs:2343
Build completed unsuccessfully in 0:00:39
make: *** [Makefile:51: check-aux] Error 1
  local time: Tue Nov 17 15:11:29 UTC 2026
  network time: Tue, 17 Nov 2026 15:11:29 GMT
##[error]Process completed with exit code 2.
##[group]Run echo "disk usage:"
echo "disk usage:"

@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

The job test-x86_64-gnu-miri failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)
[RUSTC-TIMING] rustc_crate_store test:false 0.214
error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:676:15
    |
676 |     ("sm_20", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:677:15
    |
677 |     ("sm_21", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:678:15
    |
678 |     ("sm_30", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:679:15
    |
679 |     ("sm_32", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:680:15
    |
680 |     ("sm_35", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:681:15
    |
681 |     ("sm_37", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:682:15
    |
682 |     ("sm_50", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:683:15
    |
683 |     ("sm_52", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:684:15
    |
684 |     ("sm_53", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:685:15
    |
685 |     ("sm_60", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:686:15
    |
686 |     ("sm_61", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:687:15
    |
687 |     ("sm_62", InternalOnly { reason: "unsupported compute capability", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:723:15
    |
723 |     ("ptx32", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:724:15
    |
724 |     ("ptx40", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:725:15
    |
725 |     ("ptx41", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:726:15
    |
726 |     ("ptx42", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:727:15
    |
727 |     ("ptx43", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:728:15
    |
728 |     ("ptx50", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:729:15
    |
729 |     ("ptx60", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:730:15
    |
730 |     ("ptx61", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:731:15
    |
731 |     ("ptx62", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:732:15
    |
732 |     ("ptx63", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:733:15
    |
733 |     ("ptx64", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

error[E0063]: missing field `target_modifier` in initializer of `Stability`
   --> compiler/rustc_target/src/target_features.rs:734:15
    |
734 |     ("ptx65", InternalOnly { reason: "unsupported PTX version", hard_error: true }, &[]),
    |               ^^^^^^^^^^^^ missing `target_modifier`

For more information about this error, try `rustc --explain E0063`.
[RUSTC-TIMING] rustc_target test:false 3.261
error: could not compile `rustc_target` (lib) due to 24 previous errors

@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors try cancel

@rust-bors

rust-bors Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Try build cancelled. Cancelled workflows:

Hint: if you want to run another try build, you do not need to manually cancel the previous one. Just run @bors try and bors will cancel the previous build automatically.

@rust-bors rust-bors Bot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Nov 17, 2026
@rust-bors rust-bors Bot removed the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Nov 17, 2026
@rust-bors

rust-bors Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

PR #157868, which is a member of this rollup, was unapproved.

This rollup was thus unapproved.

@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-run-make Area: port run-make Makefiles to rmake.rs rollup A PR which is a rollup T-clippy Relevant to the Clippy team. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.