Skip to content

Rollup of 5 pull requests - #160400

Merged
rust-bors[bot] merged 10 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-cXqZ0AR
Aug 2, 2026
Merged

Rollup of 5 pull requests#160400
rust-bors[bot] merged 10 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-cXqZ0AR

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Contributor

Successful merges:

r? @ghost

Create a similar rollup

Zalathar and others added 10 commits August 1, 2026 20:18
Bootstrap's `rustc` and `rustdoc` shims are mostly self-contained, but they do
share some code with each other or with other bootstrap tools.

Historically that sharing was achieved using `#[path]` attributes pointing to
the shared files. That's unusual, making the code harder to navigate, and
making dependencies and warnings harder to manage. It also causes problems for
rust-analyzer, which currently struggles with source files outside the crate
root.

This PR therefore takes two such source files, and moves them into a new
`shim_utils` crate, which can then be used as a normal crate-path dependency.
That new crate is separate from the existing `build_helper` crate, since that
crate contains other code that is not of interest to the shims specifically.

Former paths of the files that have been moved:
- `src/bootstrap/src/utils/shared_helpers.rs`
- `src/build_helper/src/arg_file_command.rs`
…aethlin

Drop elaboration: Only create a reset block if there are flags to reset.

Follow-up to rust-lang#157491

I'm not totally convinced this is worth the effort. The generated pattern is trivially cleaned-up by SimplifyCfg, so we should not need to bother.

r? @saethlin since you reviewed the earlier PR
Bump thorin-dwp (0.10), gimli (0.33), and object (0.38.1)

Originally, the hope was that this would reduce duplication of `object` within the compiler.

In practice, it turns out that this merely bumps the object major-version-set from {0.36, 0.37} to {0.37, 0.38}.

(The holdout for object@0.37 is `ar_archive_writer`, which does have a newer release available. But that would end up pulling in object@0.39 instead.)

There is still an object@0.36 entry in Cargo.lock, but that comes via `ui_test` which is a dev-dependency for clippy and miri.
bootstrap: Move some shared source files into a new `shim_utils` crate

Bootstrap's `rustc` and `rustdoc` shims are mostly self-contained, but they do share some code with each other or with other bootstrap tools.

Historically that sharing was achieved using `#[path]` attributes pointing to the shared files. That's unusual, making the code harder to navigate, and making dependencies and warnings harder to manage. It also causes problems for rust-analyzer, which currently struggles with source files outside the crate root.

This PR therefore takes two such source files, and moves them into a new `shim_utils` crate, which can then be used as a normal crate-path dependency. That new crate is separate from the existing `build_helper` crate, since that crate contains other code that is not of interest to the shims specifically.

Former paths of the files that have been moved:
- `src/bootstrap/src/utils/shared_helpers.rs`
- `src/build_helper/src/arg_file_command.rs`

---
Relevant PRs that created these shared source files:
- rust-lang#127108
- rust-lang#155439
---

r? Kobzol (or bootstrap)
…, r=jieyouxu

Assign ownership for Renovate configuration file
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Aug 2, 2026
@rustbot rustbot added A-compiletest Area: The compiletest test runner A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-meta Area: Issues & PRs about the rust-lang/rust repository itself A-run-make Area: port run-make Makefiles to rmake.rs 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-libs Relevant to the library team, which will review and decide on the PR/issue. labels Aug 2, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Contributor Author

@bors r+ rollup=never p=5

@rust-bors

rust-bors Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 2246f1e 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 Aug 2, 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 Aug 2, 2026
@rust-bors

rust-bors Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

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

@rust-bors
rust-bors Bot merged commit 11177f2 into rust-lang:main Aug 2, 2026
14 checks passed
@rustbot rustbot added this to the 1.99.0 milestone Aug 2, 2026
@rust-timer

Copy link
Copy Markdown
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#159195 Drop elaboration: Only create a reset block if there are fl… bc656657c0e2cda1e71ed39dbb9ffa75137a873d (link)
#160318 Bump thorin-dwp (0.10), gimli (0.33), and object (0.38.1) 91ce5ffa59963a6990f29b2bcfc1c6fb8bd77af8 (link)
#159756 bootstrap: Move some shared source files into a new `shim_u… 97d84af8118d2ce6ae2c2d5641e84ea1af554059 (link)
#160385 Assign ownership for Renovate configuration file 884aad968801df17b64f7d6f39ca4410284eefdf (link)
#160397 Box::new: fix safety comment 6056b0367b12b4090a26d0d8ae45a65f8f9b3543 (link)

previous master: 28c66af275

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

github-actions Bot commented Aug 2, 2026

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 28c66af (parent) -> 11177f2 (this PR)

Test differences

Show 8 test diffs

Stage 0

  • utils::tests::shared_helpers_tests::test_parse_value_from_args: pass -> [missing] (J0)
  • utils::tests::shim_utils_tests::test_parse_value_from_args: [missing] -> pass (J0)

Additionally, 6 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 11177f2235f0c842b00f82c558ad9480c0c3a895 --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. tidy: 2m 40s -> 4m 8s (+55.0%)
  2. i686-msvc-2: 1h 32m -> 2h 13m (+44.1%)
  3. test-various: 2h 3m -> 1h 17m (-37.0%)
  4. x86_64-gnu-nopt: 1h 47m -> 2h 24m (+33.6%)
  5. x86_64-gnu-gcc: 1h 8m -> 46m 39s (-32.2%)
  6. dist-aarch64-apple: 1h 27m -> 1h 52m (+28.7%)
  7. arm-android: 1h 23m -> 1h 47m (+28.6%)
  8. dist-ohos-aarch64: 1h 3m -> 1h 21m (+28.2%)
  9. i686-gnu-nopt-2: 2h 27m -> 1h 47m (-27.0%)
  10. x86_64-gnu-parallel-frontend: 1h 38m -> 2h 4m (+26.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
Copy Markdown
Collaborator

Finished benchmarking commit (11177f2): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (secondary 0.5%)

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.5% [0.4%, 0.6%] 6
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Cycles

Results (primary 0.6%, secondary -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.1% [0.4%, 3.4%] 6
Regressions ❌
(secondary)
1.0% [0.5%, 2.9%] 7
Improvements ✅
(primary)
-0.5% [-0.5%, -0.4%] 3
Improvements ✅
(secondary)
-2.8% [-3.6%, -0.8%] 4
All ❌✅ (primary) 0.6% [-0.5%, 3.4%] 9

Binary size

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

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.0% [-0.0%, -0.0%] 4
Improvements ✅
(secondary)
-0.3% [-0.6%, -0.1%] 14
All ❌✅ (primary) -0.0% [-0.0%, -0.0%] 4

Bootstrap: 490.376s -> 489.287s (-0.22%)
Artifact size: 390.46 MiB -> 390.32 MiB (-0.03%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-compiletest Area: The compiletest test runner A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-meta Area: Issues & PRs about the rust-lang/rust repository itself A-run-make Area: port run-make Makefiles to rmake.rs 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 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants