Skip to content

Rollup of 9 pull requests #143810

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 34 commits into from
Jul 12, 2025
Merged

Rollup of 9 pull requests #143810

merged 34 commits into from
Jul 12, 2025

Conversation

matthiaskrgr
Copy link
Member

@matthiaskrgr matthiaskrgr commented Jul 11, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

dillona and others added 30 commits July 8, 2025 06:24
This requires digging up ffee956
and reading the comments there to understand that the callee in
resolve_closure previously directly handled a function pointer value.
Fix a mix-up of a block with its predecessors in handling of SwitchInt
edge effects for backward analysis. Note that this functionality is
currently unused, so change has no practical impact.
Partially documents the situation due to LLVM CFI.
Those effects are untested and unused. Remove them along with
the implementation of `BasicBlocks::switch_sources`.
…jdonszelmann

Port several trait/coherence-related attributes the new attribute system

Part of rust-lang#131229

This ports:
- `#[const_trait]`
- `#[rustc_deny_explicit_impl]`
- `#[rustc_do_not_implement_via_object]`
- `#[rustc_coinductive]`
- `#[type_const]`
- `#[rustc_specialization_trait]`
- `#[rustc_unsafe_specialization_marker]`
- `#[marker]`
- `#[fundamental]`
- `#[rustc_paren_sugar]`
- `#[rustc_allow_incoherent_impl]`
- `#[rustc_coherence_is_core]`

This also changes `#[marker]` to error on duplicates instead of warning.
cc rust-lang#142838, but I don't think it matters too much, since it's unstable.

r? ``@oli-obk``
fix: correct assertion to check for 'noinline' attribute presence before removal
Clarify and expand documentation for std::sys_common dependency structure

This PR makes a minor improvement to the module-level documentation of std::sys_common:

Replaces the lowercase “dag” with the more standard and explicit form “DAG (Directed Acyclic Graph)” for clarity.
…en-backend-stuff, r=bjorn3,fee1-dead

compiler: doc/comment some codegen-for-functions interfaces

An out-of-date comment gets updated and some underdocumented functions get documented.
… r=jieyouxu

Add target maintainer information for aarch64-unknown-linux-musl

Mentioning ``@famfo`` so that they can review the documentation. We're both very invested in this target; I originally promoted it to tier 2 with host tools in rust-lang#76420 back in 2020.
Remove support for SwitchInt edge effects in backward dataflow

Those effects are untested and unused. Remove them along with the implementation of `BasicBlocks::switch_sources`.
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-rustdoc-json Area: Rustdoc JSON backend 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 Jul 11, 2025
@matthiaskrgr
Copy link
Member Author

@bors r+ rollup=never p=4

@bors
Copy link
Collaborator

bors commented Jul 11, 2025

📌 Commit 324bc31 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 Jul 11, 2025
@bors
Copy link
Collaborator

bors commented Jul 12, 2025

⌛ Testing commit 324bc31 with merge 915e535...

@bors
Copy link
Collaborator

bors commented Jul 12, 2025

☀️ Test successful - checks-actions
Approved by: matthiaskrgr
Pushing 915e535 to master...

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

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#143403 Port several trait/coherence-related attributes the new att… 496704347c3a44874ff19546271c85e555c34b6b (link)
#143633 fix: correct assertion to check for 'noinline' attribute pr… 8659a1c9641d5a760b10b6a77e6412b5f90f06b2 (link)
#143647 Clarify and expand documentation for std::sys_common depend… 876edbb89fc0aab1c0e65fa0d4d96d7236b43535 (link)
#143716 compiler: doc/comment some codegen-for-functions interfaces 9b3c2b20d834e2f688ee7ba236313beef65495cc (link)
#143747 Add target maintainer information for aarch64-unknown-linux… 22e4361562e6da20403701f2d4657c5ffbc26bed (link)
#143759 Fix typos in function names in the target_feature test 055b2f5c1f8932c2310fb527be3d7e70b669c1e5 (link)
#143767 Bump src/tools/x to Edition 2024 and some cleanups 3cec1f24119de3ac84730981fc9227387017fe7a (link)
#143769 Remove support for SwitchInt edge effects in backward dataf… c266cd4b9a3aca6b6b074687ac56a8688d217ff1 (link)
#143770 build-helper: clippy fixes 75f029a039d302000827817a60846e1a2230c204 (link)

previous master: 2f9c9cede6

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 2f9c9ce (parent) -> 915e535 (this PR)

Test differences

Show 10 test diffs

10 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 915e5352448afb3c24f89117468935283bc7d2cf --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: 75.4s -> 100.7s (33.6%)
  2. x86_64-apple-2: 5279.9s -> 3910.5s (-25.9%)
  3. x86_64-apple-1: 5989.5s -> 7098.6s (18.5%)
  4. dist-apple-various: 5714.4s -> 6730.7s (17.8%)
  5. dist-x86_64-apple: 8021.7s -> 7334.0s (-8.6%)
  6. aarch64-apple: 4625.6s -> 4978.9s (7.6%)
  7. dist-aarch64-apple: 5670.1s -> 5286.1s (-6.8%)
  8. x86_64-msvc-2: 7089.5s -> 6661.6s (-6.0%)
  9. aarch64-gnu: 6978.7s -> 6589.5s (-5.6%)
  10. arm-android: 6288.5s -> 6629.4s (5.4%)
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 (915e535): comparison URL.

Overall result: ❌✅ regressions and improvements - please read the text below

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.2% [0.1%, 0.3%] 34
Regressions ❌
(secondary)
0.4% [0.0%, 1.0%] 33
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.1% [-0.3%, -0.0%] 3
All ❌✅ (primary) 0.2% [0.1%, 0.3%] 34

Max RSS (memory usage)

Results (primary -0.9%, secondary -1.2%)

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% [1.4%, 5.6%] 2
Improvements ✅
(primary)
-0.9% [-0.9%, -0.9%] 1
Improvements ✅
(secondary)
-2.7% [-6.6%, -1.6%] 6
All ❌✅ (primary) -0.9% [-0.9%, -0.9%] 1

Cycles

Results (primary -1.8%, secondary -7.3%)

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

mean range count
Regressions ❌
(primary)
4.2% [4.2%, 4.2%] 1
Regressions ❌
(secondary)
2.8% [2.8%, 2.8%] 1
Improvements ✅
(primary)
-2.8% [-3.9%, -2.2%] 6
Improvements ✅
(secondary)
-8.8% [-11.7%, -4.6%] 7
All ❌✅ (primary) -1.8% [-3.9%, 4.2%] 7

Binary size

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

Bootstrap: 462.356s -> 466.126s (0.82%)
Artifact size: 374.66 MiB -> 374.63 MiB (-0.01%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-rustdoc-json Area: Rustdoc JSON backend merged-by-bors This PR was explicitly merged by bors. perf-regression Performance regression. 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.