Skip to content

Rollup of 8 pull requests #144658

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 21 commits into from
Jul 30, 2025
Merged

Rollup of 8 pull requests #144658

merged 21 commits into from
Jul 30, 2025

Conversation

jhpratt
Copy link
Member

@jhpratt jhpratt commented Jul 29, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

apiraino and others added 21 commits July 28, 2025 18:52
This is now printed on the same line. Use NEXT/SAME depending on
the LLVM version.
The two xors get folded into the select.
On LLVM 21 additional %esp adjustments are generated. Don't use
NEXT to allow these.
This updates the wasi-sdk used in CI to build release binaries and run
CI with. No major motivation beyond keeping things up-to-date and
following the development of wasi-sdk.
Faster equality compare

Add tests

Add missing files for tests
…buginfo, r=wesleywiser

tests: Test line number in debuginfo for diverging function calls

Closes rust-lang#59558 which just [E-needs-test](rust-lang#59558 (comment)).

The bug seems to have been fixed in **nightly-2021-05-10**:

```sh
for toolchain in nightly-2021-05-09 \
                 nightly-2021-05-10 \
                 1.88; do
    echo -e "\nWith $toolchain:"
    rustc +$toolchain tests/codegen/diverging-function-call-debuginfo.rs --emit llvm-ir -o /tmp/out.ll -g -Clto -Copt-level=0
    build/x86_64-unknown-linux-gnu/ci-llvm/bin/FileCheck --input-file /tmp/out.ll tests/codegen/diverging-function-call-debuginfo.rs --check-prefix=CHECK --dump-input-context 10 2>/dev/null && echo OK || echo FAIL
done
```

```
With nightly-2021-05-09:
FAIL

With nightly-2021-05-10:
OK

With 1.88:
OK
```

which gives the following list of candidate commits. Not clear which one it is exactly but it doesn't matter much since we can confirm that the test works. I have confirmed locally that with **nightly-2021-05-09** we get `line: 0` for the last call.

<details>
<summary>click to expand</summary>

```
$ git log ^881c1ac408d93bb7adaa3a51dabab9266e82eee8 ca82264 --no-merges --oneline
```
f25aa57 Remove unused `opt_span_warn` function
ebbc949 Note why `Handler::fatal` is different from `Sesssion::fatal`
96509b4 Make `Diagnostic::span_fatal` unconditionally raise an error
e49f447 Remove some unnecessary uses of `struct_span_fatal`
955fdae Rename `Parser::span_fatal_err` -> `Parser::span_err`
4b7c8b0 Add `#[track_caller]` to `FakeDefId::expect_real()`
ba13225 Remove `FakeDefId::expect_local()`
020d83d Enable `-W semicolon_in_expressions_from_macros` in bootstrap
1b928ff Update LLVM submodule
c2b15a6 Support -C passes in NewPM
5519cbf Don't force -O1 with ThinLTO
7c4989a Drop -opt-bisect-limit=0 flag from test
db140de Explicitly register GCOV profiling pass as well
5ecbe7f Explicitly register instrprof pass
0318883 Make -Z new-llvm-pass-manager an Option<bool>
0367e24 Avoid predecessors having Drop impls

</details>
Fix Ord, Eq and Hash implementation of panic::Location

Fixes rust-lang#144486.

Now properly compares/hashes the filename rather than the pointer to the string.
…t-nomination, r=jieyouxu,Urgau

Enable T-compiler backport nomination

This patches the triagebot.toml so that it will trigger a backport label on pull requests fixing regressions. Applying a backport label will trigger creating a Zulip thread. For now the configuration only for `T-compiler` labeled regressions.

Comments in the code explain how it works. Documentation [on the forge](https://forge.rust-lang.org/triagebot/backport.html).

```
[backport.foo]

# The pull request MUST have one of these labels
required_pr_labels = ["T-compiler"]

# The regression MUST have this label
required_issue_label = "regression-from-stable-to-beta"

# if the above conditions matches, the PR will receive these labels
add_labels = ["beta-nominated"]
```

Anything to think about before merging this?

thanks for a review
…ark-Simulacrum

Update wasi-sdk to 27.0 in CI

This updates the wasi-sdk used in CI to build release binaries and run CI with. No major motivation beyond keeping things up-to-date and following the development of wasi-sdk.
…ude, r=petrochenkov

Resolve: cachify `ExternPreludeEntry.binding` through a `Cell`

Provides interior mutability to the `binding` field of `ExternPreludeEntry` as this field behaves like a cache. Per [zulip thread](https://rust-lang.zulipchat.com/#narrow/channel/421156-gsoc/topic/Project.3A.20Parallel.20Macro.20Expansion/near/531390914).

A little preparatory work for batched import resolution, which is part of [#gsoc > Project: Parallel Macro Expansion](https://rust-lang.zulipchat.com/#narrow/channel/421156-gsoc/topic/Project.3A.20Parallel.20Macro.20Expansion).

r? `@petrochenkov`
Add support for the m68k architecture in 'object_architecture'

This is a tiny PR that adds the m68k architecture to `object_architecture`. This allows us to build rmeta files for that ISA(we use the object crate to pack metadata into object files).
@rustbot rustbot added A-CI Area: Our Github Actions CI A-meta Area: Issues & PRs about the rust-lang/rust repository itself A-testsuite Area: The testsuite used to check the correctness of rustc A-tidy Area: The tidy tool S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure 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. labels Jul 29, 2025
@jhpratt
Copy link
Member Author

jhpratt commented Jul 29, 2025

@bors r+ rollup=never p=5

@rustbot rustbot added the rollup A PR which is a rollup label Jul 29, 2025
@bors
Copy link
Collaborator

bors commented Jul 29, 2025

📌 Commit 72f4ff2 has been approved by jhpratt

It is now in the queue for this repository.

@bors bors 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 Jul 29, 2025
@bors
Copy link
Collaborator

bors commented Jul 29, 2025

⌛ Testing commit 72f4ff2 with merge c8bb4e8...

@bors
Copy link
Collaborator

bors commented Jul 30, 2025

☀️ Test successful - checks-actions
Approved by: jhpratt
Pushing c8bb4e8 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jul 30, 2025
@bors bors merged commit c8bb4e8 into rust-lang:master Jul 30, 2025
11 checks passed
@rustbot rustbot added this to the 1.90.0 milestone Jul 30, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#144034 tests: Test line number in debuginfo for diverging function… 649cd3b4ae5a2b383c2313c526752d00301d7e4d (link)
#144510 Fix Ord, Eq and Hash implementation of panic::Location 2022660e128d8b6840efb94e784145da48be295e (link)
#144583 Enable T-compiler backport nomination 0ae86bbad2e0785a8d2c5b672bf1ec674650df38 (link)
#144586 Update wasi-sdk to 27.0 in CI 6c3d470c199ecfd022ce89d50ca1111a6980c201 (link)
#144605 Resolve: cachify ExternPreludeEntry.binding through a `Ce… 0b0a8696371d13010c5874ff173070603854ddd2 (link)
#144632 Update some tests for LLVM 21 c8f190f19cf9a675cf3e363076f2e51f4abba42f (link)
#144639 Update rustc-perf submodule 647ca15e0c9bc4c9d96a44753c25aaa740a1f6fc (link)
#144640 Add support for the m68k architecture in 'object_architectu… 894fafe7925b8cc2d238f665ff6ed518f8f8b606 (link)

previous master: ba7e63b638

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

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 ba7e63b (parent) -> c8bb4e8 (this PR)

Test differences

Show 41 test diffs

Stage 1

  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 19.1.1 is older than 21.0.0) (J0)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs: ignore (ignored when the LLVM version 19.1.1 is older than 20.0.0) -> [missing] (J0)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM20: [missing] -> ignore (ignored when the LLVM version 19.1.1 is older than 20.0.0) (J0)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 19.1.1 is older than 21.0.0) (J0)
  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 20.1.2 is older than 21.0.0) (J4)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs: pass -> [missing] (J4)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM20: [missing] -> pass (J4)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 20.1.2 is older than 21.0.0) (J4)
  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs: ignore (only executed when the architecture is nvptx64) -> [missing] (J6)
  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs#LLVM20: [missing] -> ignore (only executed when the architecture is nvptx64) (J6)
  • [codegen] tests/codegen-llvm/diverging-function-call-debuginfo.rs: [missing] -> pass (J6)
  • panic::location::location_eq: [missing] -> pass (J8)
  • panic::location::location_ord: [missing] -> pass (J8)

Stage 2

  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs: ignore (only executed when the architecture is nvptx64) -> [missing] (J1)
  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs#LLVM20: [missing] -> ignore (only executed when the architecture is nvptx64) (J1)
  • [codegen] tests/codegen-llvm/diverging-function-call-debuginfo.rs: [missing] -> pass (J1)
  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 19.1.1 is older than 21.0.0) (J2)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs: ignore (ignored when the LLVM version 19.1.1 is older than 20.0.0) -> [missing] (J2)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM20: [missing] -> ignore (ignored when the LLVM version 19.1.1 is older than 20.0.0) (J2)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 19.1.1 is older than 21.0.0) (J2)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs: pass -> [missing] (J3)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM20: [missing] -> pass (J3)
  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 20.1.8 is older than 21.0.0) (J5)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 20.1.8 is older than 21.0.0) (J5)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs: ignore (only executed when the pointer width is 64bit) -> [missing] (J7)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM20: [missing] -> ignore (only executed when the pointer width is 64bit) (J7)
  • [assembly] tests/assembly-llvm/nvptx-safe-naming.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 20.1.2 is older than 21.0.0) (J9)
  • [codegen] tests/codegen-llvm/enum/enum-discriminant-eq.rs#LLVM21: [missing] -> ignore (ignored when the LLVM version 20.1.2 is older than 21.0.0) (J9)

Additionally, 13 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 c8bb4e8a126cf38cff70cea488a3a423a5321954 --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. x86_64-apple-2: 3471.8s -> 5552.5s (59.9%)
  2. dist-aarch64-apple: 5085.3s -> 7449.8s (46.5%)
  3. dist-aarch64-msvc: 5893.9s -> 8158.0s (38.4%)
  4. aarch64-msvc-1: 9107.5s -> 6304.8s (-30.8%)
  5. aarch64-apple: 5221.5s -> 6746.8s (29.2%)
  6. pr-check-2: 2126.3s -> 2708.0s (27.4%)
  7. x86_64-apple-1: 10441.2s -> 7963.5s (-23.7%)
  8. x86_64-rust-for-linux: 2609.6s -> 3187.5s (22.1%)
  9. x86_64-gnu-llvm-19: 2486.2s -> 2934.6s (18.0%)
  10. pr-check-1: 1510.1s -> 1738.4s (15.1%)
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 (c8bb4e8): comparison URL.

Overall result: ✅ improvements - 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
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.9% [-1.0%, -0.8%] 6
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary -0.4%)

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)
-2.5% [-2.5%, -2.5%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -0.4% [-2.5%, 1.6%] 2

Cycles

Results (primary 2.2%)

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

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

Binary size

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

Bootstrap: 469.063s -> 470.143s (0.23%)
Artifact size: 376.81 MiB -> 376.75 MiB (-0.01%)

github-actions bot pushed a commit to model-checking/verify-rust-std that referenced this pull request Jul 31, 2025
Rollup of 8 pull requests

Successful merges:

 - rust-lang#144034 (tests: Test line number in debuginfo for diverging function calls)
 - rust-lang#144510 (Fix Ord, Eq and Hash implementation of panic::Location)
 - rust-lang#144583 (Enable T-compiler backport nomination)
 - rust-lang#144586 (Update wasi-sdk to 27.0 in CI)
 - rust-lang#144605 (Resolve: cachify `ExternPreludeEntry.binding` through a `Cell`)
 - rust-lang#144632 (Update some tests for LLVM 21)
 - rust-lang#144639 (Update rustc-perf submodule)
 - rust-lang#144640 (Add support for the m68k architecture in 'object_architecture')

r? `@ghost`
`@rustbot` modify labels: rollup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-CI Area: Our Github Actions CI A-meta Area: Issues & PRs about the rust-lang/rust repository itself A-testsuite Area: The testsuite used to check the correctness of rustc A-tidy Area: The tidy tool merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.