Skip to content

Conversation

GuillaumeGomez
Copy link
Member

@GuillaumeGomez GuillaumeGomez commented Aug 26, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

ZhongyaoChen and others added 30 commits August 11, 2025 21:08
This will run all tests for `riscv64a23-unknown-linux-gnu` in a QEMU instance.
…u.md

Co-authored-by: zachs18 <8355914+zachs18@users.noreply.github.com>
A small oversight in 0cb69de I noticed while reading.
Losslessly optimizes all of the PNG files in the repo. Done with:

```
oxipng -o max -a -s
oxipng -o max --zopfli -a -s
```
This internal crate explicitly separates itself from the `rustc`
workspace, but it is needed for `./x test clippy` to work, including its
dependencies when building from a vendored `rustc-src` tarball.
Having `const fn`s that take a `mut &` was unstable until Rust 1.83. Because of
this, not all methods on `FormattingOptions` were implemented as `const`. As
this has been stabilized now, there is no reason not to have all methods
`const`.

Thanks to Ternvein for bringing this to my attention (see [1]).

[1]: rust-lang#118117 (comment)
The underlying implementation of `LLVMCreateConstantRangeAttribute` assumes
that each of `LowerWords` and `UpperWords` points to enough u64 values to
define an integer of the specified bit-length, and will encounter UB if that is
not the case.

Our safe wrapper function always passes pointers to `[u64; 2]` arrays,
regardless of the bit-length specified. That's fine in practice, because scalar
primitives never exceed 128 bits, but it is technically a soundness hole in a
safe function.

We can close the soundness hole by explicitly asserting `size_bits <= 128`.
This is effectively just a stricter version of the existing check that the
value must be small enough to fit in `c_uint`.
It was too dangerous to cache by default, and was it causing real bugs.
remove deprecated Error::description in impls

[libs-api permission](rust-lang/libs-team#615 (comment))

r? `@cuviper`
or `@jhpratt`
Add aarch64_be-unknown-linux-musl target

This PR adds a target definition for big-endian Aarch64 with musl-libc.

cc `@Gelbpunkt`
…cv64a23-target, r=davidtwco

Add new Tier-3 target: riscv64a23-unknown-linux-gnu

MCP: [Tier 3 target proposal: riscv64a23-unknown-linux-gnu](rust-lang/compiler-team#894)

Changes:

- add new target: riscv64a23-unknown-linux-gnu
- add target page
… r=SparrowLii

Add parentheses for closure when suggesting calling closure

Fixes rust-lang#145404
…davidtwco

Losslessly optimize PNG files

Losslessly optimizes all of the PNG files in the repo. Done with:

```
oxipng -o max -a -s
oxipng -o max --zopfli -a -s
```
…enton

Fix doc of `std::os::windows::io::BorrowedSocket::borrow_raw`

A small oversight in 0cb69de I noticed while reading.
Always build miri for the host in `x run miri`

Previously we were building Miri for the passed `--target`, which was wrong.

Fixes: rust-lang#145839

r? `@jieyouxu`
bootstrap: vendor `clippy_test_deps` too

This internal crate explicitly separates itself from the `rustc`
workspace, but it is needed for `./x test clippy` to work, including its
dependencies when building from a vendored `rustc-src` tarball.
…0250825, r=m-ou-se

formatting_options: Make all methods `const`

Related to rust-lang#118117.

Having `const fn`s that take a `mut &` was unstable until Rust 1.83 (see rust-lang#129195). Because of this, not all methods on `FormattingOptions` were implemented as `const`. As this has been stabilized now, there is no reason not to have all methods `const`.

Thanks to `@Ternvein` for bringing this to my attention (see [1]).

r? `@m-ou-se` (As you were the reviewer for the original implementation – feel free to reroll if you are busy or if you aren't interested)

[1]: rust-lang#118117 (comment)
cg_llvm: Assert that LLVM range-attribute values don't exceed 128 bits

The underlying implementation of `LLVMCreateConstantRangeAttribute` assumes that each of `LowerWords` and `UpperWords` points to enough u64 values to define an integer of the specified bit-length, and will encounter UB if that is not the case.

Our safe wrapper function always passes pointers to `[u64; 2]` arrays, regardless of the bit-length specified. That's fine in practice, because scalar primitives never exceed 128 bits, but it is technically a soundness hole in a safe function.

We can close the soundness hole by explicitly asserting `size_bits <= 128`. This is effectively just a stricter version of the existing check that the value must be small enough to fit in `c_uint`.

---

This is a narrower version of the fix in rust-lang#145846.
@rustbot rustbot added O-hermit Operating System: Hermit O-SGX Target: SGX O-solid Operating System: SOLID O-unix Operating system: Unix-like O-wasi Operating system: Wasi, Webassembly System Interface O-windows Operating system: Windows 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-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. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. labels Aug 26, 2025
@GuillaumeGomez
Copy link
Member Author

@bors r+ p=5 rollup=never

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

bors commented Aug 26, 2025

📌 Commit 0f30dcc has been approved by GuillaumeGomez

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 Aug 26, 2025
@bors
Copy link
Collaborator

bors commented Aug 26, 2025

⌛ Testing commit 0f30dcc with merge 91ee6a4...

@bors
Copy link
Collaborator

bors commented Aug 26, 2025

☀️ Test successful - checks-actions
Approved by: GuillaumeGomez
Pushing 91ee6a4 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Aug 26, 2025
@bors bors merged commit 91ee6a4 into rust-lang:master Aug 26, 2025
11 checks passed
@rustbot rustbot added this to the 1.91.0 milestone Aug 26, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#144373 remove deprecated Error::description in impls c74f2a5731dc3904907f097f2a52ed5c9bd34f8c (link)
#144551 Add aarch64_be-unknown-linux-musl target e55337d25e3a640149211607ff5dc811552154f2 (link)
#145076 Add new Tier-3 target: riscv64a23-unknown-linux-gnu 455a4eb6e2a8434c5873e6abd1466485a0958d4a (link)
#145481 Add parentheses for closure when suggesting calling closure 61d396fd0dd6f519b9bbd42cb27384337df055e2 (link)
#145596 Losslessly optimize PNG files 16c83b56f1ea1257ad0cc8cb2355fc3e2a11b143 (link)
#145615 Fix doc of `std::os::windows::io::BorrowedSocket::borrow_ra… 29c58188dc8d071ea08b8174dbab66c36da8cb7b (link)
#145841 Always build miri for the host in x run miri 08eb3c37a043d720dbd4356ea4e518ab66e7106b (link)
#145861 bootstrap: vendor clippy_test_deps too 04f1bf839cd61e5a78fd1225a03f1d8c66b6c670 (link)
#145863 formatting_options: Make all methods const 7da0b507d3a9f1dded743626b50b215a59f9c068 (link)
#145867 cg_llvm: Assert that LLVM range-attribute values don't exce… 284aaa3484406ead0ac3bc955618669173b02929 (link)
#145875 Make bootstrap command caching opt-in 1411abfd97363fbaa4a8769a63f862cef31324c2 (link)

previous master: 5ab69249f3

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 5ab6924 (parent) -> 91ee6a4 (this PR)

Test differences

Show 215 test diffs

Stage 0

  • core::builder::tests::snapshot::run_miri: [missing] -> pass (J1)

Stage 1

  • spec::tests::aarch64_be_unknown_linux_musl: [missing] -> pass (J1)
  • spec::tests::riscv64a23_unknown_linux_gnu: [missing] -> pass (J1)
  • [assembly] tests/assembly-llvm/targets/targets-elf.rs#aarch64_be_unknown_linux_musl: [missing] -> pass (J2)
  • [assembly] tests/assembly-llvm/targets/targets-elf.rs#riscv64a23_unknown_linux_gnu: [missing] -> pass (J2)
  • [ui] tests/ui/suggestions/use-parentheses-to-call-closure-issue-145404.rs: [missing] -> pass (J2)

Stage 2

  • [assembly] tests/assembly-llvm/targets/targets-elf.rs#aarch64_be_unknown_linux_musl: [missing] -> pass (J0)
  • [assembly] tests/assembly-llvm/targets/targets-elf.rs#riscv64a23_unknown_linux_gnu: [missing] -> pass (J0)
  • [ui] tests/ui/suggestions/use-parentheses-to-call-closure-issue-145404.rs: [missing] -> pass (J3)

Additionally, 206 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 91ee6a4057ce4bf1ab6d2f932cae497488d67c81 --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-linux: 6437.1s -> 8868.2s (37.8%)
  2. dist-apple-various: 4224.8s -> 5250.0s (24.3%)
  3. x86_64-gnu-aux: 6239.9s -> 7515.0s (20.4%)
  4. i686-gnu-nopt-1: 7292.8s -> 8413.8s (15.4%)
  5. i686-gnu-2: 5440.0s -> 6247.9s (14.9%)
  6. aarch64-gnu-llvm-19-1: 3314.9s -> 3714.9s (12.1%)
  7. test-various: 4729.2s -> 5279.2s (11.6%)
  8. arm-android: 5894.2s -> 6489.2s (10.1%)
  9. x86_64-gnu-distcheck: 5179.8s -> 5684.6s (9.7%)
  10. x86_64-gnu-debug: 6394.2s -> 7010.5s (9.6%)
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 (91ee6a4): 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.9% [-0.9%, -0.9%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -0.9% [-0.9%, -0.9%] 1

Max RSS (memory usage)

Results (primary 0.7%, secondary 3.7%)

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

mean range count
Regressions ❌
(primary)
1.5% [0.5%, 2.5%] 3
Regressions ❌
(secondary)
3.7% [2.8%, 4.3%] 4
Improvements ✅
(primary)
-1.7% [-1.7%, -1.7%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.7% [-1.7%, 2.5%] 4

Cycles

Results (primary 4.2%, secondary -0.6%)

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

mean range count
Regressions ❌
(primary)
4.2% [2.5%, 5.9%] 2
Regressions ❌
(secondary)
2.5% [2.2%, 3.0%] 4
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-3.0% [-3.4%, -2.2%] 5
All ❌✅ (primary) 4.2% [2.5%, 5.9%] 2

Binary size

Results (primary -0.1%, secondary -0.0%)

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

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-0.1% [-0.4%, -0.1%] 6
Improvements ✅
(secondary)
-0.0% [-0.0%, -0.0%] 1
All ❌✅ (primary) -0.1% [-0.4%, -0.1%] 6

Bootstrap: 466.377s -> 469.036s (0.57%)
Artifact size: 391.17 MiB -> 391.17 MiB (-0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-testsuite Area: The testsuite used to check the correctness of rustc merged-by-bors This PR was explicitly merged by bors. O-hermit Operating System: Hermit O-SGX Target: SGX O-solid Operating System: SOLID O-unix Operating system: Unix-like O-wasi Operating system: Wasi, Webassembly System Interface O-windows Operating system: Windows 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-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. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.
Projects
None yet
Development

Successfully merging this pull request may close these issues.