Skip to content

Rollup of 8 pull requests#152627

Merged
rust-bors[bot] merged 26 commits intorust-lang:mainfrom
JonathanBrouwer:rollup-wjHXhK0
Feb 14, 2026
Merged

Rollup of 8 pull requests#152627
rust-bors[bot] merged 26 commits intorust-lang:mainfrom
JonathanBrouwer:rollup-wjHXhK0

Conversation

@JonathanBrouwer
Copy link
Contributor

Successful merges:

r? @ghost

Create a similar rollup

folkertdev and others added 26 commits February 2, 2026 15:53
The `vldap1` and `vstl1` RCPC3 intrinsics introduced in standard library unconditionally use `AtomicI64`. This breaks builds on target that do not support 64-bit atomics, such as `aarch64-unknown-none` with `max-atomic-width` set to 0. This commit adds a `#[cfg(target_has_atomic = "64")]` guard to these intrinsics
…cated-saturating-stores

x86: use `intrinsics::simd` for masked truncated saturating stores
aarch64: use `read_unaligned` for `vld1_*`
aarch64: Guard RCPC3 intrinsics with target_has_atomic = "64"
Co-authored-by: Boxy <rust@boxyuwu.dev>
Relocate LitToConstInput and const_lit_matches_ty from mir::interpret
to ty::consts::lit
mGCA: Validate const literal against expected type

close: rust-lang#151625
close: rust-lang#150983

also fix: rust-lang#133966 (moved crashes test)
…etrochenkov

Don't ICE on layout error in vtable computation

Fixes rust-lang#152030.

Note: I'm including a more general testcase that doesn't use the feature in the original report, but only reproduces with debuginfo disabled. Does it make sense to also include the original testcase?
…petrochenkov

`proc_macro::bridge`: simplify `ExecutionStrategy` and `DispatcherTrait`

Also includes another tiny cleanup (functions can only have one return type).
…uwer

Port #[rustc_proc_macro_decls] to the new attribute parser.

Tracking issue: rust-lang#131229

r? @JonathanBrouwer
…uwer

Port #[rustc_test_marker] to the attribute parser

Tracking issue: rust-lang#131229

Targets:
Const is for normal tests (const test::TestDescAndFn is inserted before the test fn)
Const/Static/Fn is for custom_test_framework's #[test_case] e.g. tests/ui/custom_test_frameworks/full.rs

r? @JonathanBrouwer

Again I left the use-sites as is since they are early uses.
DepGraphQuery: correctly skip adding edges with not-yet-added nodes

Fixes rust-lang#142152.

The current logic already skips some edges, so I'm not sure how critical it is to have *all* the edges recorded, the logic seems to only be used for debug dumping.
Recording all edges requires supporting holes in the `LinkedGraph` data structure, to add nodes and edges out of order, rust-lang#151821 implements that at cost of complicating the data structure.
…donszelmann

Rename `inline_fluent!` to `msg!`

This was the most popular name for the macro as voted in [#t-compiler > Bikeshed the new &rust-lang#96;inline_fluent!&rust-lang#96; macro @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Bikeshed.20the.20new.20.60inline_fluent!.60.20macro/near/572751863)
@rust-bors rust-bors bot added the rollup A PR which is a rollup label Feb 14, 2026
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-translation Area: Translation infrastructure, and migrating existing diagnostics to SessionDiagnostic labels Feb 14, 2026
@rustbot rustbot added 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-rust-analyzer Relevant to the rust-analyzer team, which will review and decide on the PR/issue. labels Feb 14, 2026
@JonathanBrouwer
Copy link
Contributor Author

@bors r+ rollup=never p=5

@rust-bors
Copy link
Contributor

rust-bors bot commented Feb 14, 2026

📌 Commit 38cc50b 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 Feb 14, 2026
@rust-bors rust-bors bot mentioned this pull request Feb 14, 2026
@rust-bors

This comment has been minimized.

@rust-bors rust-bors bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Feb 14, 2026
@rust-bors
Copy link
Contributor

rust-bors bot commented Feb 14, 2026

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 14m 17s
Pushing a33907a to main...

@rust-bors rust-bors bot merged commit a33907a into rust-lang:main Feb 14, 2026
12 checks passed
@rustbot rustbot added this to the 1.95.0 milestone Feb 14, 2026
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#152001 mGCA: Validate const literal against expected type b5fd2a5b8fa814c5b66236dae4aaf6c47ba91c7a (link)
#152120 Don't ICE on layout error in vtable computation 2443d2606413e2c8035183d9b5c9d5d99c84766e (link)
#152531 proc_macro::bridge: simplify ExecutionStrategy and `Dis… 54cf6f6186123f700709e0641f0c249eab1bf585 (link)
#152570 Port #[rustc_test_marker] to the attribute parser 56c8245766346f8b88f02282082cb0533d9fd3aa (link)
#152577 Port #[rustc_proc_macro_decls] to the new attribute parser. 168b1ffaa42e914a7b709c9c25a24ac462dc736b (link)
#152590 DepGraphQuery: correctly skip adding edges with not-yet-add… d725c2fd3c4e7cac465905472fcafa0c60f8bfb4 (link)
#152612 Rename inline_fluent! to msg! a2f2fdd9569139f0d40b822e8617f7c9793749c1 (link)
#152618 stdarch subtree update 57ab5e517cb74a56f572c7637a2ebdec537e2940 (link)

previous master: f8463896a9

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

@github-actions
Copy link
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 f846389 (parent) -> a33907a (this PR)

Test differences

Show 40 test diffs

Stage 1

  • [crashes] tests/crashes/133966.rs: pass -> [missing] (J1)
  • [ui] tests/ui/const-generics/generic_const_exprs/lit_type_mismatch.rs: pass -> [missing] (J1)
  • [ui] tests/ui/const-generics/mgca/generic_const_type_mismatch.rs: [missing] -> pass (J1)
  • [ui] tests/ui/const-generics/mgca/nonsensical-negated-literal.rs: [missing] -> pass (J1)
  • [ui] tests/ui/const-generics/mgca/tuple_expr_type_mismatch.rs: [missing] -> pass (J1)
  • [ui] tests/ui/consts/const-eval/array-len-mismatch-type.rs: [missing] -> pass (J1)
  • [ui] tests/ui/limits/vtable-try-as-dyn.rs#full-debuginfo: [missing] -> pass (J1)
  • [ui] tests/ui/limits/vtable-try-as-dyn.rs#no-debuginfo: [missing] -> pass (J1)
  • [ui] tests/ui/limits/vtable.rs: [missing] -> pass (J1)

Stage 2

  • [ui] tests/ui/const-generics/generic_const_exprs/lit_type_mismatch.rs: pass -> [missing] (J0)
  • [ui] tests/ui/const-generics/mgca/generic_const_type_mismatch.rs: [missing] -> pass (J0)
  • [ui] tests/ui/const-generics/mgca/nonsensical-negated-literal.rs: [missing] -> pass (J0)
  • [ui] tests/ui/const-generics/mgca/tuple_expr_type_mismatch.rs: [missing] -> pass (J0)
  • [ui] tests/ui/consts/const-eval/array-len-mismatch-type.rs: [missing] -> pass (J0)
  • [ui] tests/ui/limits/vtable-try-as-dyn.rs#full-debuginfo: [missing] -> pass (J0)
  • [ui] tests/ui/limits/vtable-try-as-dyn.rs#no-debuginfo: [missing] -> pass (J0)
  • [ui] tests/ui/limits/vtable.rs: [missing] -> pass (J0)
  • [crashes] tests/crashes/133966.rs: pass -> [missing] (J2)

Additionally, 22 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 a33907a7a5381473eec8bcfa0c56e05a856a911c --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: 1h 52m -> 2h 48m (+50.5%)
  2. dist-apple-various: 1h 40m -> 2h 21m (+40.2%)
  3. pr-check-2: 34m 56s -> 42m 44s (+22.3%)
  4. pr-check-1: 27m 53s -> 33m 54s (+21.6%)
  5. x86_64-gnu-stable: 2h 1m -> 2h 27m (+20.8%)
  6. arm-android: 1h 30m -> 1h 45m (+16.5%)
  7. x86_64-rust-for-linux: 45m 56s -> 52m 50s (+15.0%)
  8. aarch64-gnu-llvm-20-1: 56m 38s -> 1h 5m (+15.0%)
  9. i686-gnu-1: 2h 1m -> 2h 19m (+14.5%)
  10. aarch64-gnu-llvm-20-2: 44m 48s -> 51m 2s (+13.9%)
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
Collaborator

Finished benchmarking commit (a33907a): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

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

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
0.5% [0.5%, 0.5%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary 1.2%, secondary 1.0%)

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

mean range count
Regressions ❌
(primary)
3.1% [1.5%, 5.6%] 3
Regressions ❌
(secondary)
2.4% [2.3%, 2.5%] 2
Improvements ✅
(primary)
-1.8% [-2.3%, -1.3%] 2
Improvements ✅
(secondary)
-1.9% [-1.9%, -1.9%] 1
All ❌✅ (primary) 1.2% [-2.3%, 5.6%] 5

Cycles

Results (primary 1.6%, secondary -3.3%)

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

mean range count
Regressions ❌
(primary)
1.6% [1.6%, 1.6%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-3.3% [-3.3%, -3.3%] 1
All ❌✅ (primary) 1.6% [1.6%, 1.6%] 1

Binary size

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

Bootstrap: 480.91s -> 483.617s (0.56%)
Artifact size: 397.91 MiB -> 397.94 MiB (0.01%)

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-translation Area: Translation infrastructure, and migrating existing diagnostics to SessionDiagnostic merged-by-bors This PR was explicitly merged by bors. 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-rust-analyzer Relevant to the rust-analyzer team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.