Skip to content

Rollup of 12 pull requests - #149351

Merged
bors merged 33 commits into
rust-lang:mainfrom
Zalathar:rollup-ee06zha
Nov 26, 2025
Merged

Rollup of 12 pull requests#149351
bors merged 33 commits into
rust-lang:mainfrom
Zalathar:rollup-ee06zha

Conversation

@Zalathar

@ZalatharZalathar commented Nov 26, 2025

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

Fulgen301and others added 30 commits November 3, 2025 19:54
instead of legacy mangling to avoid linker errors
Co-authored-by: teor <teor@riseup.net>
ARM has withdrawn FEAT_TME
https://developer.arm.com/documentation/102105/lb-05/
LLVM has dropped support for it recently as a result.
This works better with non-LLVM codegen backends.
This is required for the soundness of options(may_unwind)
Also, use `Vec::resize` instead of individual `push`es
Offload intrinsic
This PR implements the minimal mechanisms required to run a small subset of arbitrary offload kernels without relying on hardcoded names or metadata.
- `offload(kernel, (..args))`: an intrinsic that generates the necessary host-side LLVM-IR code.
- `rustc_offload_kernel`: a builtin attribute that marks device kernels to be handled appropriately.
Example usage (pseudocode):
```rust
fn kernel(x: *mut [f64; 128]) {
core::intrinsics::offload(kernel_1, (x,))
}
#[cfg(target_os = "linux")]
extern "C" {
pub fn kernel_1(array_b: *mut [f64; 128]);
}
#[cfg(not(target_os = "linux"))]
#[rustc_offload_kernel]
extern "gpu-kernel" fn kernel_1(x: *mut [f64; 128]) {
unsafe { (*x)[0] = 21.0 };
}
```
Fix some issues around `rustc_public`
cc rust-lang#148266 .
follow-up of rust-lang#148341 .
This fixes the issues that can be reproduced by `x test compiler/rustc_public`:
```
error: function `run` is never used
--> compiler/rustc_public/src/compiler_interface.rs:838:15
|
838 | pub(crate) fn run<'tcx, F, T>(interface: &CompilerInterface<'tcx>, f: F) -> Result<T, Error>
| ^^^
|
= note: `-D dead-code` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(dead_code)]`
error: unreachable `pub` item
--> compiler/rustc_public/src/unstable/mod.rs:25:1
|
25 | pub trait InternalCx<'tcx>: Copy + Clone {
| ---^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| |
| help: consider restricting its visibility: `pub(crate)`
|
= help: or consider exporting it for use by other crates
= note: `-D unreachable-pub` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(unreachable_pub)]`
error: unreachable `pub` item
--> compiler/rustc_public/src/unstable/mod.rs:62:1
|
62 | pub trait Stable<'tcx>: PointeeSized {
| ---^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| |
| help: consider restricting its visibility: `pub(crate)`
|
= help: or consider exporting it for use by other crates
error: unreachable `pub` item
--> compiler/rustc_public/src/unstable/mod.rs:81:1
|
81 | pub trait RustcInternal {
| ---^^^^^^^^^^^^^^^^^^^^
| |
| help: consider restricting its visibility: `pub(crate)`
|
= help: or consider exporting it for use by other crates
error: could not compile `rustc_public` (lib) due to 4 previous errors
```
…jackh726
Mangle symbols with a mangled name close to PDB limits with v0 instead of legacy mangling to avoid linker errors
This is rust-lang/compiler-team#934
As PDB debuginfo has a 64KiB limit for symbol names, we use v0 mangling instead of legacy mangling for symbol names >= 65000 bytes if PDB is used. The cutoff number was chosen to leave some room for potential errors in the empirical measurement of the limit of 65521 bytes, as well as potential symbol prefixes and suffixes that are applied later, plus some generous extra space.
Tracking issue: rust-lang#148429
…rcoieni
Build gnullvm toolchains on Windows natively
Fixesrust-lang#144656
rustc_target: aarch64: Remove deprecated FEAT_TME
fixesrust-lang#149308
ARM has withdrawn FEAT_TME
https://developer.arm.com/documentation/102105/lb-05/
LLVM has dropped support for generating it
llvm/llvm-project#167687
```@rustbot``` label llvm-main
r? ```@durin42```
…/misc-cleanups, r=GuillaumeGomez
[rustdoc] misc search index cleanups
Bunch of misc cleanups to search index generation (on the rustdoc side). Perf isn't improved unfortunately, but I do think most of these changes are improvements to readability/style.
Probably easier to review commit by commit.
…r=RalfJung
Use rust rather than LLVM target features in the target spec
This works better with non-LLVM codegen backends.
…, r=fmease
Deny const auto traits
closerust-lang#149285
The AST validation now detects and rejects const auto traits. Additionally, I updated an existing test that was using `const unsafe auto trait`.
r? fmease
…ywiser
Mark riscv64gc-unknown-linux-musl as tier 2 target
According to https://github.com/rust-lang/rust/blob/cdb4236e654a49c3035269588fe22dfafc0cfa3a/src/doc/rustc/src/platform-support/riscv64gc-unknown-linux-musl.md?plain=1#L3 it's tier 2 target.
In case you are wondering how I noticed it:
Dockerfiles at Wild linker repo started to fail building recently due to missing `riscv64gc-unknown-linux-musl` std. I had hoped the problem would go away by itself, but it did not (it never does...).
rust-lang#148983 happened recently, so I checked https://rust-lang.github.io/rustup-components-history/riscv64gc-unknown-linux-musl.html and yeah, the date matches.
Given this condition: https://github.com/rust-lang/rust/blob/cdb4236e654a49c3035269588fe22dfafc0cfa3a/src/tools/build-manifest/build.rs#L35 I'm certain PR will fix the problem.
@borsbors 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 26, 2025
@Zalathar

Copy link
Copy Markdown
MemberAuthor

Double-checking that this doesn't (currently) run into #149342 (comment):

@bors try jobs=test-various

@rust-bors

This comment has been minimized.

rust-borsBot added a commit that referenced this pull request Nov 26, 2025
Rollup of 12 pull requests
try-job: test-various
@rust-bors

rust-borsBot commented Nov 26, 2025

Copy link
Copy Markdown
Contributor

☀️ Try build successful (CI)
Build commit: 9bb8959 (9bb8959ff35721f27174d7a9eb5141e102a14b89, parent: 6840234806e4a57e14112a1137783c885b7a23db)

@bors

bors commented Nov 26, 2025

Copy link
Copy Markdown
Collaborator

⌛ Testing commit 4a05348 with merge 99ca3fc...

@bors

bors commented Nov 26, 2025

Copy link
Copy Markdown
Collaborator

☀️ Test successful - checks-actions
Approved by: Zalathar
Pushing 99ca3fc to main...

@borsbors added the merged-by-bors This PR was explicitly merged by bors. label Nov 26, 2025
@bors
bors merged commit 99ca3fc into rust-lang:mainNov 26, 2025
13 checks passed
@rustbotrustbot added this to the 1.93.0 milestone Nov 26, 2025
@github-actions

Copy link
Copy Markdown
Contributor
What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing c797096 (parent) -> 99ca3fc (this PR)

Test differences

Show 188 test diffs

Stage 0

  • errors::verify_ast_passes_abi_cannot_be_coroutine_69: [missing] -> pass (J1)
  • errors::verify_ast_passes_abi_custom_safe_foreign_function_66: pass -> [missing] (J1)
  • errors::verify_ast_passes_abi_custom_safe_foreign_function_67: [missing] -> pass (J1)
  • errors::verify_ast_passes_abi_must_not_have_parameters_or_return_type_70: [missing] -> pass (J1)
  • errors::verify_ast_passes_abi_x86_interrupt_71: pass -> [missing] (J1)
  • errors::verify_ast_passes_abi_x86_interrupt_72: [missing] -> pass (J1)
  • errors::verify_ast_passes_at_least_one_trait_40: pass -> [missing] (J1)
  • errors::verify_ast_passes_at_least_one_trait_41: [missing] -> pass (J1)
  • errors::verify_ast_passes_const_and_c_variadic_54: [missing] -> pass (J1)
  • errors::verify_ast_passes_const_and_coroutine_52: pass -> [missing] (J1)
  • errors::verify_ast_passes_const_auto_trait_37: [missing] -> pass (J1)
  • errors::verify_ast_passes_const_bound_trait_object_51: pass -> [missing] (J1)
  • errors::verify_ast_passes_const_bound_trait_object_52: [missing] -> pass (J1)
  • errors::verify_ast_passes_coroutine_and_c_variadic_54: pass -> [missing] (J1)
  • errors::verify_ast_passes_extern_without_abi_sugg_65: pass -> [missing] (J1)
  • errors::verify_ast_passes_extern_without_abi_sugg_66: [missing] -> pass (J1)
  • errors::verify_ast_passes_fieldless_union_47: pass -> [missing] (J1)
  • errors::verify_ast_passes_fieldless_union_48: [missing] -> pass (J1)
  • errors::verify_ast_passes_incompatible_features_58: [missing] -> pass (J1)
  • errors::verify_ast_passes_missing_unsafe_on_extern_45: pass -> [missing] (J1)
  • errors::verify_ast_passes_missing_unsafe_on_extern_lint_46: pass -> [missing] (J1)
  • errors::verify_ast_passes_missing_unsafe_on_extern_lint_47: [missing] -> pass (J1)
  • errors::verify_ast_passes_negative_bound_not_supported_58: pass -> [missing] (J1)
  • errors::verify_ast_passes_negative_bound_not_supported_59: [missing] -> pass (J1)
  • errors::verify_ast_passes_negative_bound_with_parenthetical_notation_60: pass -> [missing] (J1)
  • errors::verify_ast_passes_nested_impl_trait_40: [missing] -> pass (J1)
  • errors::verify_ast_passes_nested_lifetimes_51: [missing] -> pass (J1)
  • errors::verify_ast_passes_obsolete_auto_42: pass -> [missing] (J1)
  • errors::verify_ast_passes_obsolete_auto_43: [missing] -> pass (J1)
  • errors::verify_ast_passes_pattern_in_bodiless_57: [missing] -> pass (J1)
  • errors::verify_ast_passes_pattern_in_fn_pointer_37: pass -> [missing] (J1)
  • errors::verify_ast_passes_precise_capturing_duplicated_63: pass -> [missing] (J1)
  • errors::verify_ast_passes_precise_capturing_duplicated_64: [missing] -> pass (J1)
  • errors::verify_ast_passes_precise_capturing_not_allowed_here_62: pass -> [missing] (J1)
  • errors::verify_ast_passes_precise_capturing_not_allowed_here_63: [missing] -> pass (J1)
  • errors::verify_ast_passes_trait_object_single_bound_38: pass -> [missing] (J1)
  • errors::verify_ast_passes_unsafe_item_44: pass -> [missing] (J1)
  • errors::verify_ast_passes_unsafe_item_45: [missing] -> pass (J1)
  • errors::verify_ast_passes_unsafe_negative_impl_44: [missing] -> pass (J1)
  • errors::verify_ast_passes_where_clause_after_type_alias_48: pass -> [missing] (J1)
  • errors::verify_mir_transform_ffi_unwind_call_6: pass -> [missing] (J1)
  • errors::verify_mir_transform_ffi_unwind_call_7: [missing] -> pass (J1)
  • errors::verify_mir_transform_fn_item_ref_7: pass -> [missing] (J1)
  • errors::verify_mir_transform_unused_assign_passed_10: [missing] -> pass (J1)
  • errors::verify_mir_transform_unused_capture_maybe_capture_ref_8: pass -> [missing] (J1)

Stage 1

  • errors::verify_ast_passes_abi_cannot_be_coroutine_68: pass -> [missing] (J0)
  • errors::verify_ast_passes_abi_cannot_be_coroutine_69: [missing] -> pass (J0)
  • errors::verify_ast_passes_abi_must_not_have_parameters_or_return_type_69: pass -> [missing] (J0)
  • errors::verify_ast_passes_abi_must_not_have_parameters_or_return_type_70: [missing] -> pass (J0)
  • errors::verify_ast_passes_abi_must_not_have_return_type_70: pass -> [missing] (J0)
  • errors::verify_ast_passes_abi_must_not_have_return_type_71: [missing] -> pass (J0)
  • errors::verify_ast_passes_abi_x86_interrupt_71: pass -> [missing] (J0)
  • errors::verify_ast_passes_at_least_one_trait_40: pass -> [missing] (J0)
  • errors::verify_ast_passes_at_least_one_trait_41: [missing] -> pass (J0)
  • errors::verify_ast_passes_const_and_c_variadic_53: pass -> [missing] (J0)
  • errors::verify_ast_passes_const_and_c_variadic_54: [missing] -> pass (J0)
  • errors::verify_ast_passes_const_and_coroutine_52: pass -> [missing] (J0)
  • errors::verify_ast_passes_const_and_coroutine_53: [missing] -> pass (J0)
  • errors::verify_ast_passes_const_bound_trait_object_51: pass -> [missing] (J0)
  • errors::verify_ast_passes_const_bound_trait_object_52: [missing] -> pass (J0)
  • errors::verify_ast_passes_constraint_on_negative_bound_59: pass -> [missing] (J0)
  • errors::verify_ast_passes_constraint_on_negative_bound_60: [missing] -> pass (J0)
  • errors::verify_ast_passes_coroutine_and_c_variadic_55: [missing] -> pass (J0)
  • errors::verify_ast_passes_extern_without_abi_64: pass -> [missing] (J0)
  • errors::verify_ast_passes_extern_without_abi_sugg_65: pass -> [missing] (J0)
  • errors::verify_ast_passes_fieldless_union_47: pass -> [missing] (J0)
  • errors::verify_ast_passes_fieldless_union_48: [missing] -> pass (J0)
  • errors::verify_ast_passes_incompatible_features_58: [missing] -> pass (J0)
  • errors::verify_ast_passes_match_arm_with_no_body_61: pass -> [missing] (J0)
  • errors::verify_ast_passes_match_arm_with_no_body_62: [missing] -> pass (J0)
  • errors::verify_ast_passes_missing_unsafe_on_extern_45: pass -> [missing] (J0)
  • errors::verify_ast_passes_missing_unsafe_on_extern_46: [missing] -> pass (J0)
  • errors::verify_ast_passes_missing_unsafe_on_extern_lint_47: [missing] -> pass (J0)
  • errors::verify_ast_passes_negative_bound_not_supported_58: pass -> [missing] (J0)
  • errors::verify_ast_passes_negative_bound_not_supported_59: [missing] -> pass (J0)
  • errors::verify_ast_passes_nested_impl_trait_39: pass -> [missing] (J0)
  • errors::verify_ast_passes_nested_impl_trait_40: [missing] -> pass (J0)
  • errors::verify_ast_passes_nested_lifetimes_51: [missing] -> pass (J0)
  • errors::verify_ast_passes_obsolete_auto_42: pass -> [missing] (J0)
  • errors::verify_ast_passes_out_of_order_params_42: [missing] -> pass (J0)
  • errors::verify_ast_passes_pattern_in_bodiless_57: [missing] -> pass (J0)
  • errors::verify_ast_passes_pattern_in_fn_pointer_37: pass -> [missing] (J0)
  • errors::verify_ast_passes_precise_capturing_duplicated_64: [missing] -> pass (J0)
  • errors::verify_ast_passes_precise_capturing_not_allowed_here_62: pass -> [missing] (J0)
  • errors::verify_ast_passes_precise_capturing_not_allowed_here_63: [missing] -> pass (J0)
  • errors::verify_ast_passes_unsafe_item_44: pass -> [missing] (J0)
  • errors::verify_ast_passes_where_clause_after_type_alias_48: pass -> [missing] (J0)
  • errors::verify_ast_passes_where_clause_after_type_alias_49: [missing] -> pass (J0)
  • errors::verify_mir_transform_ffi_unwind_call_6: pass -> [missing] (J0)
  • errors::verify_mir_transform_ffi_unwind_call_7: [missing] -> pass (J0)
  • errors::verify_mir_transform_fn_item_ref_7: pass -> [missing] (J0)
  • errors::verify_mir_transform_fn_item_ref_8: [missing] -> pass (J0)
  • errors::verify_mir_transform_unused_assign_passed_10: [missing] -> pass (J0)
  • errors::verify_mir_transform_unused_assign_passed_9: pass -> [missing] (J0)
  • errors::verify_mir_transform_unused_capture_maybe_capture_ref_8: pass -> [missing] (J0)
  • [ui] tests/ui/offload/check_config.rs#fail: [missing] -> ignore (ignored when LLVM Enzyme is disabled or LLVM is not the default codegen backend) (J1)
  • [ui] tests/ui/offload/check_config.rs#pass: [missing] -> ignore (ignored when LLVM Enzyme is disabled or LLVM is not the default codegen backend) (J1)

Stage 2

  • [ui] tests/ui/asm/may_unwind_ffi_unwind.rs: [missing] -> pass (J2)
  • [ui] tests/ui/offload/check_config.rs#pass: [missing] -> ignore (ignored when LLVM Enzyme is disabled or LLVM is not the default codegen backend) (J2)
  • [ui] tests/ui/traits/const-traits/const-auto-trait.rs: [missing] -> pass (J2)

(and 68 additional test diffs)

Additionally, 20 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 99ca3fc4ec35e11d1f034143e8d8f0b79ef4c1d7 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. dist-aarch64-apple: 6563.4s -> 7798.0s (+18.8%)
  2. dist-armhf-linux: 5265.8s -> 4477.9s (-15.0%)
  3. dist-powerpc64le-linux-musl: 5219.9s -> 5856.5s (+12.2%)
  4. x86_64-mingw-1: 10476.7s -> 9266.9s (-11.5%)
  5. dist-apple-various: 3772.7s -> 4185.7s (+10.9%)
  6. dist-arm-linux-gnueabi: 4782.4s -> 5298.6s (+10.8%)
  7. x86_64-gnu-llvm-20-2: 5933.8s -> 5367.1s (-9.6%)
  8. dist-x86_64-solaris: 5058.2s -> 5502.8s (+8.8%)
  9. x86_64-gnu-llvm-20: 2907.3s -> 2676.1s (-8.0%)
  10. x86_64-gnu-miri: 4794.8s -> 4440.2s (-7.4%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer

Copy link
Copy Markdown
Collaborator

📌 Perf builds for each rolled up PR:

PR#MessagePerf Build Sha
#147936Offload intrinsic29cfccd2ae67ca24d2df1cc2f08eea5b347dde69 (link)
#148358Fix some issues around rustc_public2c7bc7c78d68295e55372dd113f3d0fb91d60775 (link)
#148452Mangle symbols with a mangled name close to PDB limits with…a1ca8aa5f4fd53458fc1bdafe4162e63d7d9c2d7 (link)
#148751Build gnullvm toolchains on Windows nativelyf55680d189796f517dfd2a330c6f799be65f5657 (link)
#148951rustc_target: aarch64: Remove deprecated FEAT_TME0717bfbbc17ebb700e56138fb1069c527aaca01f (link)
#149149[rustdoc] misc search index cleanups05faf4ccc5a569073079fb8ec68da99530ae2e74 (link)
#149173Use rust rather than LLVM target features in the target specb85362cbb0da056c9b6b3456c67b2d7108d9b203 (link)
#149307Deny const auto traits4973be0804b422088f7ef7b310a897b4abd93d0a (link)
#149312Mark riscv64gc-unknown-linux-musl as tier 2 targetc3628415dd30a86fad7798c985bdcbe82b08ac66 (link)
#149317Handle inline asm in has_ffi_unwind_calls8d526a64bed83c72db09c7a5d406ed39389d1be9 (link)
#149326Remove unused Clone derive on DelayedLint14860cf5eb8b9ce84a602a6056630d300b59249c (link)
#149341Add Copy to some AST enums.438ce382764c9dca85c486b217c482e3ac487dc0 (link)

previous master: c797096598

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (99ca3fc): comparison URL.

Overall result: ❌ regressions - please read the text below

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

  • If the regression was expected or you think it can be justified,
    please write a comment with sufficient written justification, and add
    @rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
  • If you think that you know of a way to resolve the regression, try to create
    a new PR with a fix for the regression.
  • If you do not understand the regression or you think that it is just noise,
    you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
    were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

meanrangecount
Regressions ❌
(primary)
0.1%[0.1%, 0.1%]1
Regressions ❌
(secondary)
0.8%[0.3%, 1.3%]8
Improvements ✅
(primary)
--0
Improvements ✅
(secondary)
--0
All ❌✅ (primary)0.1%[0.1%, 0.1%]1

Max RSS (memory usage)

Results (secondary -3.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

meanrangecount
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
--0
Improvements ✅
(primary)
--0
Improvements ✅
(secondary)
-3.9%[-3.9%, -3.9%]1
All ❌✅ (primary)--0

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 470.439s -> 475.097s (0.99%)
Artifact size: 386.94 MiB -> 386.96 MiB (0.01%)

@rustbotrustbot added the perf-regression Performance regression. label Nov 26, 2025
@Zalathar
Zalathar deleted the rollup-ee06zha branch November 26, 2025 22:37
@Zalathar

Copy link
Copy Markdown
MemberAuthor

@rust-timer

This comment has been minimized.

@rust-timer

This comment was marked as resolved.

@Zalathar

Copy link
Copy Markdown
MemberAuthor

@rust-timer

This comment has been minimized.

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (29cfccd): comparison URL.

Overall result: ❌ regressions - please read the text below

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

meanrangecount
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
0.7%[0.3%, 1.3%]8
Improvements ✅
(primary)
--0
Improvements ✅
(secondary)
--0
All ❌✅ (primary)--0

Max RSS (memory usage)

This benchmark run did not return any relevant results for this metric.

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 470.439s -> 469.615s (-0.18%)
Artifact size: 386.94 MiB -> 386.92 MiB (-0.00%)

@ZalatharZalathar mentioned this pull request Nov 27, 2025
@Mark-SimulacrumMark-Simulacrum added the perf-regression-triaged The performance regression has been triaged. label Dec 3, 2025
makai410 pushed a commit to makai410/rust that referenced this pull request Dec 10, 2025
Rollup of 12 pull requests
Successful merges:
- rust-lang#147936 (Offload intrinsic)
- rust-lang#148358 (Fix some issues around `rustc_public`)
- rust-lang#148452 (Mangle symbols with a mangled name close to PDB limits with v0 instead of legacy mangling to avoid linker errors)
- rust-lang#148751 (Build gnullvm toolchains on Windows natively)
- rust-lang#148951 (rustc_target: aarch64: Remove deprecated FEAT_TME)
- rust-lang#149149 ([rustdoc] misc search index cleanups)
- rust-lang#149173 (Use rust rather than LLVM target features in the target spec)
- rust-lang#149307 (Deny const auto traits)
- rust-lang#149312 (Mark riscv64gc-unknown-linux-musl as tier 2 target)
- rust-lang#149317 (Handle inline asm in has_ffi_unwind_calls)
- rust-lang#149326 (Remove unused `Clone` derive on `DelayedLint`)
- rust-lang#149341 (Add `Copy` to some AST enums.)
r? `@ghost`
`@rustbot` modify labels: rollup
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-attributesArea: Attributes (`#[…]`, `#![…]`)A-CIArea: Our Github Actions CIA-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.A-rustc-dev-guideArea: rustc-dev-guideA-testsuiteArea: The testsuite used to check the correctness of rustcmerged-by-borsThis PR was explicitly merged by bors.perf-regressionPerformance regression.perf-regression-triagedThe performance regression has been triaged.rollupA PR which is a rollupS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.T-rustdoc-frontendRelevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.WG-trait-system-refactorThe Rustc Trait System Refactor Initiative (-Znext-solver)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

15 participants

@Zalathar@bors@rust-timer@Mark-Simulacrum@rustbot@Fulgen301@makai410@mati865@maurer@lapla-cogito@bjorn3@Sa4dUs@JonathanBrouwer@Jarcho@yotamofek