Skip to content

Conversation

@JonathanBrouwer
Copy link
Contributor

@JonathanBrouwer JonathanBrouwer commented Dec 17, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

androm3da and others added 8 commits December 14, 2025 19:54
Implements proper variadic argument handling for hexagon-unknown-linux-musl
targets using a 3-pointer VaList structure compatible with LLVM's
HexagonBuiltinVaList implementation.

* Handles register save area vs overflow area transition
* Provides proper 4-byte and 8-byte alignment for arguments
* Only activates for hexagon+musl targets via Arch::Hexagon & Env::Musl
Pointing out they can set the crate's name is non-actionable:
their problem is they found out how and set it incorrectly.
Remove extraneous information that can only confuse the matter.
…rtdev

Implement va_arg for Hexagon targets

Implements proper variadic argument handling for hexagon-unknown-linux-musl targets using a 3-pointer VaList structure compatible with LLVM's HexagonBuiltinVaList implementation.

* Handles register save area vs overflow area transition
* Provides proper 4-byte and 8-byte alignment for arguments
* Only activates for hexagon+musl targets via Arch::Hexagon & Env::Musl
…relevant-rename, r=jieyouxu

Avoid unhelpful suggestion when crate name is invalid

Pointing out they can set the crate's name is non-actionable: their problem is they found out how and set it incorrectly. Remove extraneous information that can only confuse the matter.
…inter, r=JonathanBrouwer

Port `#[rustc_never_returns_null_ptr]` to attribute parser

Ports `#[rustc_never_returns_null_ptr]` to be parsed using the attribute parser

r? `@JonathanBrouwer`
@rustbot rustbot added A-attributes Area: Attributes (`#[…]`, `#![…]`) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Dec 17, 2025
@JonathanBrouwer
Copy link
Contributor Author

@bors r+ rollup=never p=5

@bors
Copy link
Collaborator

bors commented Dec 17, 2025

📌 Commit 84d441f has been approved by JonathanBrouwer

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 Dec 17, 2025
@bors
Copy link
Collaborator

bors commented Dec 17, 2025

⌛ Testing commit 84d441f with merge 68f11a1...

@bors
Copy link
Collaborator

bors commented Dec 17, 2025

☀️ Test successful - checks-actions
Approved by: JonathanBrouwer
Pushing 68f11a1 to main...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Dec 17, 2025
@bors bors merged commit 68f11a1 into rust-lang:main Dec 17, 2025
12 checks passed
@rustbot rustbot added this to the 1.94.0 milestone Dec 17, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#150008 Implement va_arg for Hexagon targets f8c1a47c59827d953a70ea3c3bbd535621cf536c (link)
#150044 Avoid unhelpful suggestion when crate name is invalid fa5729cac9e20df5067dee3068f6a8dac814794f (link)
#150086 Port #[rustc_never_returns_null_ptr] to attribute parser d3c7f80e60f23900a2b9457f3b01c810a159e844 (link)

previous master: f2c70877a7

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
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 f2c7087 (parent) -> 68f11a1 (this PR)

Test differences

Show 13 test diffs

Stage 2

  • [run-make] tests/run-make/compressed-debuginfo-zstd: ignore (ignored if LLVM wasn't build with zstd for ELF section compression or LLVM is not the default codegen backend) -> pass (J0)

Additionally, 12 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 68f11a11b666b36137374b6e54fc0d013a3b26cf --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-apple: 9387.0s -> 7744.3s (-17.5%)
  2. x86_64-gnu-gcc: 4094.3s -> 3424.9s (-16.3%)
  3. x86_64-rust-for-linux: 3733.9s -> 3135.8s (-16.0%)
  4. pr-check-2: 3069.3s -> 2637.2s (-14.1%)
  5. x86_64-gnu-llvm-21-2: 5247.4s -> 5985.6s (+14.1%)
  6. i686-gnu-1: 7509.2s -> 8531.1s (+13.6%)
  7. dist-powerpc64le-linux-musl: 5749.6s -> 5037.9s (-12.4%)
  8. x86_64-gnu-nopt: 9912.4s -> 8722.5s (-12.0%)
  9. dist-x86_64-apple: 7429.7s -> 8291.9s (+11.6%)
  10. i686-gnu-2: 5294.2s -> 5902.3s (+11.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
Collaborator

Finished benchmarking commit (68f11a1): comparison URL.

Overall result: ❌ regressions - 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.8% [0.2%, 1.1%] 3
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary 2.7%, secondary 1.6%)

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

mean range count
Regressions ❌
(primary)
2.7% [2.4%, 2.9%] 2
Regressions ❌
(secondary)
1.6% [0.7%, 2.3%] 3
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 2.7% [2.4%, 2.9%] 2

Cycles

Results (primary 2.7%, secondary -2.4%)

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

mean range count
Regressions ❌
(primary)
2.7% [2.2%, 3.2%] 2
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-2.4% [-2.7%, -2.1%] 2
All ❌✅ (primary) 2.7% [2.2%, 3.2%] 2

Binary size

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

Bootstrap: 483.372s -> 483.218s (-0.03%)
Artifact size: 390.57 MiB -> 390.58 MiB (0.00%)

@JonathanBrouwer
Copy link
Contributor Author

@rust-timer build d3c7f80

@rust-timer

This comment has been minimized.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (d3c7f80): comparison URL.

Overall result: no relevant changes - BENCHMARK(S) FAILED

❗ ❗ ❗ ❗ ❗
Warning ⚠️: The following benchmark(s) failed to build:

  • Job failure

❗ ❗ ❗ ❗ ❗

Instruction count

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

Max RSS (memory usage)

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

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: missing data
Artifact size: missing data

@JonathanBrouwer
Copy link
Contributor Author

@rust-timer build d3c7f80

@JonathanBrouwer
Copy link
Contributor Author

@rust-timer build d3c7f80

@JonathanBrouwer
Copy link
Contributor Author

@rust-timer ping

@rust-timer
Copy link
Collaborator

Command cannot be empty

@JonathanBrouwer
Copy link
Contributor Author

@rust-timer build d3c7f80

@JonathanBrouwer
Copy link
Contributor Author

Ok one more try
@rust-timer build d3c7f80

@Kobzol
Copy link
Member

Kobzol commented Dec 17, 2025

You have to ask nicely!

Please:

@rust-timer build d3c7f80

@rust-timer

This comment has been minimized.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (d3c7f80): comparison URL.

Overall result: no relevant changes - no action needed

Instruction count

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

Max RSS (memory usage)

Results (primary 3.0%, secondary 1.0%)

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

mean range count
Regressions ❌
(primary)
3.0% [2.3%, 3.7%] 2
Regressions ❌
(secondary)
1.8% [1.7%, 2.0%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.8% [-0.8%, -0.8%] 1
All ❌✅ (primary) 3.0% [2.3%, 3.7%] 2

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: 483.372s -> 482.536s (-0.17%)
Artifact size: 390.57 MiB -> 390.56 MiB (-0.00%)

@JonathanBrouwer
Copy link
Contributor Author

I don't see the other 2 PRs affecting perf, and the perf graphs of the affected benchmarks do look kinda noisy, so I'm calling this noise then

@Kobzol
Copy link
Member

Kobzol commented Dec 17, 2025

Yeah, it's fine. It wasn't even marked as a regression previously.

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. 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-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants