Skip to content

Rollup of 9 pull requests #141954

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 36 commits into from
Jun 3, 2025
Merged

Rollup of 9 pull requests #141954

merged 36 commits into from
Jun 3, 2025

Conversation

matthiaskrgr
Copy link
Member

@matthiaskrgr matthiaskrgr commented Jun 3, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

vremyavnikuda and others added 30 commits May 26, 2025 15:51
fix: Recognize salsa cycles in `thread_result_to_response`
fix: Fix import insertion not being fully cfg aware
…efs-constructor-search

docs: add documentation for find_all_refs constructor search
internal: Restructure some semantics APIs for virtual macro files
refactor: Remove unncessary duplication in highlight_related
Account for `Generate` actions when filtering the allowed ones
fix: Fix manual not containing diagnostics documentation
…ndows

This obviously doesn't work when cross-compiling from Linux.

Split out from: rust-lang#140772
This helps with efforts to deduplicate the `MutVisitor` and the
`Visitor` code. All users of `Visitor`'s methods that have extra
`NodeId` as parameters really just want to visit the id on its
own.

Also includes some methods deduplicated and cleaned up as
a result of this change.
This adds more information to many different codegen options. It should
not add any new guarantees, just document existing behavior.
This disables the f64 minimum/maximum tests for the
arm-unknown-linux-gnueabihf job. The next release will be supporting
cross-compiled doctests, and these tests fail on that platform.

It looks like this was just fixed via
llvm/llvm-project#142170, but I assume that will
not trickle down to our copy of llvm in the next couple of weeks.
Assuming that does get fixed when llvm is updated, then these can be
removed.

cc rust-lang#141087
Obviously `test-float-parse` is a tool like any other in `src/tools`.

Signed-off-by: onur-ozkan <[email protected]>
…tter, r=bjorn3

Improve documentation for codegen options

This adds more information to many different codegen options. It should not add any new guarantees, just document existing behavior.

r? bjorn3
…-compiling, r=cuviper

rustc_llvm: add Windows system libs only when cross-compiling from Wi…

…ndows

This obviously doesn't work when cross-compiling from Linux.

Split out from: rust-lang#140772

Fixes the issue described at [#general > Problems while trying to cross compile rustc for windows](https://rust-lang.zulipchat.com/#narrow/channel/122651-general/topic/Problems.20while.20trying.20to.20cross.20compile.20rustc.20for.20windows/with/520508561)
…t_id, r=oli-obk

Add `visit_id` to ast `Visitor`

This helps with efforts to deduplicate the `MutVisitor` and the `Visitor` code. All users of `Visitor`'s methods that have extra `NodeId` as parameters really just want to visit the id on its own.

Also includes some methods deduplicated and cleaned up as a result of this change.

r? oli-obk
…ling, r=oli-obk

Decouple "reporting in deps" from `FutureIncompatibilityReason`

The reason should just be it -- the reason. It never felt right to me that it was also responsible for whatever we include the warning in cargo's reports.

It gets especially unruly if you want to add non-`FutureReleaseError*` warnings which are included in the reports.

I just added a field to `FutureIncompatibleInfo` to control whatever the diagnostic is included in the cargo's reports.
…r=Kobzol

move `test-float-parse` tool into `src/tools` dir

Obviously `test-float-parse` is a tool like any other in `src/tools`.

cc `@tgross35`
@rustbot rustbot added 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-rustdoc-json Area: Rustdoc JSON backend 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. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Jun 3, 2025
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Jun 3, 2025

📌 Commit 2fa33b0 has been approved by matthiaskrgr

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 Jun 3, 2025
@bors
Copy link
Collaborator

bors commented Jun 3, 2025

⌛ Testing commit 2fa33b0 with merge 2f17612...

@bors
Copy link
Collaborator

bors commented Jun 3, 2025

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 2f17612 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jun 3, 2025
@bors bors merged commit 2f17612 into rust-lang:master Jun 3, 2025
11 checks passed
@rustbot rustbot added this to the 1.89.0 milestone Jun 3, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#141554 Improve documentation for codegen options 3dcb6cf921951c1b396e2fe5407b0f252dcb0853 (link)
#141817 rustc_llvm: add Windows system libs only when cross-compili… 0b55b506f6a95f12697e65cd13a9793abaad3b1f (link)
#141843 Add visit_id to ast Visitor 5590a8cb9e8477eb2637f35ec4d54141ed79ed81 (link)
#141881 Subtree update of rust-analyzer 6c875cc6552c67ea4c5e844ba9bf618903af5dbd (link)
#141898 [rustdoc-json] Implement PartialOrd and Ord for rustdoc_typ… f21c96f240490602bcfa450ded61cfb5699a9856 (link)
#141921 Disable f64 minimum/maximum tests for arm 32 7b9193444b3fb74393975771a48f4525acf4891e (link)
#141930 Enable triagebot [concern] functionality 1133bf285e739fc5537c9eea58b7d90a4efa8852 (link)
#141936 Decouple "reporting in deps" from `FutureIncompatibilityRea… 00a762964417ce943ef46496b666aa3e2e4203ad (link)
#141949 move test-float-parse tool into src/tools dir 60430d066f1add256682997411f2255f280a0176 (link)

previous master: c68032fd4c

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

github-actions bot commented Jun 3, 2025

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 c68032f (parent) -> 2f17612 (this PR)

Test differences

Show 278 test diffs

278 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 2f176126aaf3fd316fc5ced3d9a111a48797b52c --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-1: 8415.5s -> 6848.4s (-18.6%)
  2. x86_64-apple-2: 6250.0s -> 5161.8s (-17.4%)
  3. dist-s390x-linux: 5196.7s -> 5626.9s (8.3%)
  4. dist-aarch64-apple: 6086.7s -> 6519.2s (7.1%)
  5. dist-apple-various: 7753.8s -> 7333.7s (-5.4%)
  6. i686-msvc-2: 7548.0s -> 7188.9s (-4.8%)
  7. aarch64-gnu-debug: 3998.6s -> 3829.7s (-4.2%)
  8. i686-gnu-nopt-2: 6496.9s -> 6736.8s (3.7%)
  9. x86_64-gnu-llvm-20-1: 3883.5s -> 3744.0s (-3.6%)
  10. x86_64-gnu-llvm-19-1: 3828.0s -> 3690.5s (-3.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 (2f17612): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

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

Max RSS (memory usage)

Results (secondary 2.7%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
4.3% [1.4%, 7.3%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.6% [-0.6%, -0.6%] 1
All ❌✅ (primary) - - 0

Cycles

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

Binary size

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

Bootstrap: 743.521s -> 744.283s (0.10%)
Artifact size: 372.32 MiB -> 372.30 MiB (-0.01%)

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-meta Area: Issues & PRs about the rust-lang/rust repository itself A-rustdoc-json Area: Rustdoc JSON backend 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-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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.