Skip to content

Rollup of 13 pull requests#159246

Merged
rust-bors[bot] merged 55 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-ZywyNke
Jul 13, 2026
Merged

Rollup of 13 pull requests#159246
rust-bors[bot] merged 55 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-ZywyNke

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Contributor

Successful merges:

r? @ghost

Create a similar rollup

qaijuang and others added 30 commits June 12, 2026 20:57
There is only one place where `SourceKindSubdiag` is used without
`SourceKindMultiSuggestion`; it doesn't seem useful to distinguish
between them (I have no idea what either of the names means tbh)
This allows users of `rustc_public` to do more complex navigation
through data structures by exposing the following info:

* `AdtDef::generics_of` - Get the generics for the ADT.
* `AdtDef::inherent_impls` - Get all the impls for the ADT.
* `FnDef::associated_item` - Get the trait or impl block that contains the
  function if it exists.
* `FnDef::generics_of` - get the generics for a given function.
* `ImplDef::generics_of` - Get the generics for the impl block.
* `ImplDef` implements `CrateDefType` - figure out the type of the impl
  block with `CrateDefType::ty()` or get the normalized type with
`CrateDefType::ty_with_args()`.

This was partially written with the help of Gemini, but I reviewed the
code it generated.
@rust-bors

rust-bors Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 768fb02 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 Jul 13, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Jul 13, 2026
Rollup of 13 pull requests


try-job: dist-various-1
try-job: test-various
try-job: x86_64-gnu-aux
try-job: x86_64-gnu-llvm-21-3
try-job: x86_64-msvc-1
try-job: aarch64-apple
try-job: x86_64-mingw-1
try-job: i686-msvc-*
@rust-bors

This comment has been minimized.

@rust-bors

rust-bors Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

☀️ Try build successful (CI)
Build commit: ff710d5 (ff710d5e2127f77e8a49cf8a2612d4577ab6453d)
Base parent: 225e91c (225e91c03da22cd4b9792b83c1cfc97967101614)

@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 Jul 13, 2026
@rust-bors

rust-bors Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 4h 51m 14s
Pushing daf2e5e to main...

@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 225e91c (parent) -> daf2e5e (this PR)

Test differences

Show 187 test diffs

Stage 0

  • style::tests::test_file_ignore_precedence: [missing] -> pass (J6)
  • style::tests::test_tidy_style_unused_directive: [missing] -> pass (J6)
  • style::tests::test_tidy_style_unused_file_directive: [missing] -> pass (J6)
  • style::tests::test_tidy_todo_usage_ignored_correctly: [missing] -> pass (J6)
  • style::tests::test_tidy_todo_usage_ignored_correctly_file: [missing] -> pass (J6)
  • style::tests::test_tidy_todo_usage_ignored_correctly_file_line_inbetween: [missing] -> pass (J6)
  • style::tests::test_tidy_todo_usage_ignored_wrong_line: [missing] -> pass (J6)

Stage 1

  • [ui (polonius)] tests/ui/const_prop/mir-opt-impossible-sized-predicates.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/delegation/method-probe-self-ty-infer-var.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/eii/linking/track_caller_cross_crate.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/eii/track_caller.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/eii/track_caller_errors.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/eii/track_caller_static_errors.rs: [missing] -> pass (J0)
  • [ui (polonius)] tests/ui/lint/unused/unused-never-binding-issue-158783.rs: [missing] -> pass (J0)
  • [ui] tests/ui/const_prop/mir-opt-impossible-sized-predicates.rs: [missing] -> pass (J7)
  • [ui] tests/ui/delegation/method-probe-self-ty-infer-var.rs: [missing] -> pass (J7)
  • [ui] tests/ui/eii/linking/track_caller_cross_crate.rs: [missing] -> pass (J7)
  • [ui] tests/ui/eii/track_caller.rs: [missing] -> pass (J7)
  • [ui] tests/ui/eii/track_caller_errors.rs: [missing] -> pass (J7)
  • [ui] tests/ui/eii/track_caller_static_errors.rs: [missing] -> pass (J7)
  • [ui] tests/ui/lint/unused/unused-never-binding-issue-158783.rs: [missing] -> pass (J7)
  • [ui] tests/ui-fulldeps/rustc_public/check_alias.rs: [missing] -> ignore (ignored when the bootstrapping stage is stage1) (J9)
  • [ui] tests/ui-fulldeps/rustc_public/check_generics.rs: [missing] -> ignore (ignored when the bootstrapping stage is stage1) (J9)
  • [ui] tests/ui-fulldeps/rustc_public/check_inherent_impls.rs: [missing] -> ignore (ignored when the bootstrapping stage is stage1) (J9)
  • [ui] tests/ui-fulldeps/test_entrypoint_attrs.rs: [missing] -> ignore (ignored when the bootstrapping stage is stage1) (J9)

Stage 2

  • [ui] tests/ui/eii/track_caller_static_errors.rs: [missing] -> ignore (ignored when the target vendor is Apple) (J1)
  • [ui] tests/ui-fulldeps/rustc_public/check_alias.rs: [missing] -> pass (J2)
  • [ui] tests/ui-fulldeps/rustc_public/check_generics.rs: [missing] -> pass (J2)
  • [ui] tests/ui-fulldeps/rustc_public/check_inherent_impls.rs: [missing] -> pass (J2)
  • [ui] tests/ui-fulldeps/test_entrypoint_attrs.rs: [missing] -> pass (J2)
  • [ui] tests/ui/const_prop/mir-opt-impossible-sized-predicates.rs: [missing] -> pass (J3)
  • [ui] tests/ui/delegation/method-probe-self-ty-infer-var.rs: [missing] -> pass (J3)
  • [ui] tests/ui/eii/track_caller_errors.rs: [missing] -> pass (J3)
  • [ui] tests/ui/lint/unused/unused-never-binding-issue-158783.rs: [missing] -> pass (J3)
  • [ui] tests/ui/eii/linking/track_caller_cross_crate.rs: [missing] -> ignore (ignored when the operating system is windows) (J4)
  • [ui] tests/ui/eii/track_caller.rs: [missing] -> ignore (ignored when the operating system is windows) (J4)
  • [ui] tests/ui/eii/track_caller_static_errors.rs: [missing] -> pass (J5)
  • [ui] tests/ui/eii/linking/track_caller_cross_crate.rs: [missing] -> pass (J8)
  • [ui] tests/ui/eii/track_caller.rs: [missing] -> pass (J8)
  • [ui] tests/ui/eii/linking/track_caller_cross_crate.rs: [missing] -> ignore (gcc backend is marked as ignore) (J10)
  • [ui] tests/ui/eii/track_caller.rs: [missing] -> ignore (gcc backend is marked as ignore) (J10)

Additionally, 146 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 daf2e5e18b3abc4311d9da3d96fd64138f43d508 --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. aarch64-apple: 2h 24m -> 3h 40m (+52.7%)
  2. dist-x86_64-apple: 1h 26m -> 2h 4m (+43.5%)
  3. x86_64-msvc-2: 1h 50m -> 2h 27m (+34.3%)
  4. x86_64-mingw-2: 1h 57m -> 2h 37m (+34.0%)
  5. armhf-gnu: 1h 6m -> 1h 29m (+33.8%)
  6. x86_64-msvc-ext1: 1h 32m -> 2h 1m (+32.1%)
  7. x86_64-gnu-gcc: 49m 32s -> 1h 4m (+29.6%)
  8. dist-apple-various: 2h 2m -> 1h 27m (-28.4%)
  9. x86_64-gnu-llvm-21: 1h 15m -> 55m 55s (-25.7%)
  10. dist-x86_64-musl: 2h 13m -> 1h 42m (-23.5%)
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# Message Perf Build Sha
#157706 Deny todo!() in tidy 8a2d434b4c4919059cda7e7da3fbea377324326a (link)
#158535 Support #[track_caller] on EII declarations 5183945874e51a0a1613fdd30b26235b2faf5abe (link)
#158632 First steps of late-bound turbofishing (place FnDef behind … d60257152691cf12ffefeee3ceac0913c1873ff6 (link)
#158846 Fix unused variable warnings for diverging expressions 58515823a7ecd52b86786de7a47093e8c0b722a6 (link)
#159002 Small refactorings in need_type_info module 3281f09585058f63e89b9a01c0c9d2ad26e7ca0e (link)
#159202 Bump rustc-demangle to 0.1.28 6159f49dd8a5007939eb972b127e2049b7c6af82 (link)
#159216 Avoid using probe self_ty for delegation arguments c1b628cc9c42b34a3ec6794252576144863ffd8e (link)
#156609 Consider structurally impossible Sized predicates in MIR 25028da70c0c5a425749b218f10c95877f44781c (link)
#157993 Expose more info about ADTs and functions in rustc_public 45fbcd083a8e28b651735e2825f88160e52bb9d1 (link)
#158804 Clarify as_uninit_mut may point to uninitialized memory f1b5e5af7674f2c7236b14d481cbb773ef13526b (link)
#158854 Add #[rustc_test_entrypoint_marker] 8b11920afd2b5fae563bffc80f6705ff238b99e3 (link)
#158998 Some minor ast validation and visiting cleanups be6cb91e5869320cd1f8dc19f7308f57520bb7db (link)
#159123 doc: clarify attr parser APIs 92ba3c0fecfcd78cdfefab995e372a05372a24f9 (link)

previous master: 225e91c03d

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 (daf2e5e): comparison URL.

Overall result: ❌ regressions - please read:

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.

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

Max RSS (memory usage)

Results (primary 1.3%, 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)
1.3% [0.8%, 1.8%] 2
Regressions ❌
(secondary)
1.5% [0.9%, 2.8%] 4
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-2.1% [-4.1%, -0.9%] 5
All ❌✅ (primary) 1.3% [0.8%, 1.8%] 2

Cycles

Results (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)
- - 0
Regressions ❌
(secondary)
3.5% [2.8%, 4.8%] 3
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-3.7% [-5.4%, -2.1%] 2
All ❌✅ (primary) - - 0

Binary size

Results (primary 0.1%, secondary 0.1%)

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

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

Bootstrap: 488.117s -> 490.521s (0.49%)
Artifact size: 389.87 MiB -> 389.35 MiB (-0.13%)

@rustbot rustbot added the perf-regression Performance regression. label Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-attributes Area: Attributes (`#[…]`, `#![…]`) A-CI Area: Our Github Actions CI A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-run-make Area: port run-make Makefiles to rmake.rs A-rustdoc-js Area: Rustdoc's JS front-end A-rustdoc-json Area: Rustdoc JSON backend A-rustdoc-search Area: Rustdoc's search feature A-test-infra-minicore Area: `minicore` test auxiliary and `//@ add-core-stubs` 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. O-windows Operating system: Windows perf-regression Performance regression. PG-exploit-mitigations Project group: Exploit mitigations rollup A PR which is a rollup T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-clippy Relevant to the Clippy team. 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. 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. WG-trait-system-refactor The Rustc Trait System Refactor Initiative (-Znext-solver)

Projects

None yet

Development

Successfully merging this pull request may close these issues.