Skip to content

Rollup of 3 pull requests#159170

Merged
rust-bors[bot] merged 9 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-UxyQ0Ig
Jul 12, 2026
Merged

Rollup of 3 pull requests#159170
rust-bors[bot] merged 9 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-UxyQ0Ig

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Contributor

Successful merges:

r? @ghost

Create a similar rollup

scottmcm and others added 9 commits July 11, 2026 12:03
Otherwise 32-bit has a different ABI and the `CHECK` fails.
And the noopt job fails without forcing MIR optimization here.
Fix offset used to read the second part of scalar pairs from a `const`

Fixes rust-lang#159116

r? @workingjubilee
…r=workingjubilee

c-variadic: Update cfg for 128-bit integers to fix build error on AArch64 ILP32

This fixes build error on AArch64 ILP32 targets (aarch64-unknown-linux-gnu_ilp32, aarch64_be-unknown-linux-gnu_ilp32, arm64_32-apple-watchos) introduced in rust-lang#155429. See rust-lang#155429 (comment) for details.

The approach used in this PR (use exact cfgs instead of using a rough cfgs with checking unexpected case by `compile_error!`) is also based on what was proposed in that comment. The set of allowed cases should not be changed in this PR.

cc @folkertdev

@rustbot label +O-aarch64 +F-c_variadic
… r=JonathanBrouwer

Rename `errors.rs` file to `diagnostics.rs` (12/N)

Follow-up of rust-lang#157485.

r? @JonathanBrouwer
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Jul 12, 2026
@rustbot rustbot added 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. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Jul 12, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Contributor Author

@bors r+ rollup=never p=5

@rust-bors

rust-bors Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

📌 Commit b5718d0 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 12, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Jul 12, 2026
…uwer

Rollup of 3 pull requests

Successful merges:

 - #159148 (Fix offset used to read the second part of scalar pairs from a `const`)
 - #159167 (c-variadic: Update cfg for 128-bit integers to fix build error on AArch64 ILP32)
 - #159153 (Rename `errors.rs` file to `diagnostics.rs` (12/N))
@rust-log-analyzer

Copy link
Copy Markdown
Collaborator

The job x86_64-gnu-nopt failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)
test [debuginfo-gdb] tests/debuginfo/zst-interferes-with-prologue.rs ... ok

failures:

---- [debuginfo-gdb] tests/debuginfo/function-call.rs stdout ----
NOTE: compiletest thinks it is using GDB version 12001000
------gdb stdout------------------------------
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04.2) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Breakpoint 1 at 0x1b42: file /checkout/tests/debuginfo/function-call.rs, line 36.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, function_call::main () at /checkout/tests/debuginfo/function-call.rs:36
36     zzz(); // #break

------gdb stderr------------------------------
/checkout/obj/build/x86_64-unknown-linux-gnu/test/debuginfo/function-call.gdb/function-call.debugger.script:11: Error in sourced command file:
Couldn't write extended state status: Bad address.

------------------------------------------

error: gdb failed to execute
status: exit status: 1
command: PYTHONPATH="/checkout/src/etc" "/usr/bin/gdb" "-quiet" "-batch" "-nx" "-command=/checkout/obj/build/x86_64-unknown-linux-gnu/test/debuginfo/function-call.gdb/function-call.debugger.script"
--- stdout -------------------------------
GNU gdb (Ubuntu 12.1-0ubuntu1~22.04.2) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Breakpoint 1 at 0x1b42: file /checkout/tests/debuginfo/function-call.rs, line 36.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, function_call::main () at /checkout/tests/debuginfo/function-call.rs:36
36     zzz(); // #break
------------------------------------------
--- stderr -------------------------------
/checkout/obj/build/x86_64-unknown-linux-gnu/test/debuginfo/function-call.gdb/function-call.debugger.script:11: Error in sourced command file:
Couldn't write extended state status: Bad address.
------------------------------------------

@rust-bors rust-bors Bot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jul 12, 2026
@rust-bors

rust-bors Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

💔 Test for 170e61f failed: CI. Failed job:

@JonathanBrouwer

Copy link
Copy Markdown
Contributor Author

@bors retry

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

rust-bors Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 11m 16s
Pushing babf6ea to main...

@rust-timer

Copy link
Copy Markdown
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#159148 Fix offset used to read the second part of scalar pairs fro… a242f50a629c9090a169541badc2138ccb57079e (link)
#159167 c-variadic: Update cfg for 128-bit integers to fix build er… f94f126028d7322f4c28daf8fddfefa81fde720e (link)
#159153 Rename errors.rs file to diagnostics.rs (12/N) 804cd8f915cfec787581da43d7259f43a3026926 (link)

previous master: b69e089eb3

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
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 b69e089 (parent) -> babf6ea (this PR)

Test differences

Show 32 test diffs

Stage 1

  • [codegen] tests/codegen-llvm/const-array-of-pairs.rs: [missing] -> pass (J1)

Stage 2

  • [codegen] tests/codegen-llvm/const-array-of-pairs.rs: [missing] -> pass (J0)

Additionally, 30 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 babf6ea4aab9ed78ea9400b25b0e7e79a6870f29 --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-gnu-gcc-core-tests: 14m 45s -> 8m 3s (-45.4%)
  2. x86_64-rust-for-linux: 54m 43s -> 35m 34s (-35.0%)
  3. i686-gnu-2: 1h 42m -> 1h 7m (-34.1%)
  4. x86_64-gnu-miri: 1h 39m -> 1h 6m (-32.8%)
  5. x86_64-gnu-aux: 2h 56m -> 2h 1m (-31.0%)
  6. test-various: 2h 16m -> 1h 34m (-30.9%)
  7. pr-check-1: 33m 38s -> 23m 37s (-29.7%)
  8. x86_64-msvc-2: 2h 29m -> 1h 45m (-29.6%)
  9. dist-x86_64-solaris: 1h 18m -> 1h 39m (+28.0%)
  10. x86_64-gnu-debug: 2h 8m -> 1h 32m (-27.9%)
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 (babf6ea): comparison URL.

Overall result: ✅ improvements - 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
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.1% [-0.2%, -0.0%] 11
All ❌✅ (primary) - - 0

Max RSS (memory usage)

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

Cycles

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

Binary size

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

Bootstrap: 489.358s -> 490.525s (0.24%)
Artifact size: 389.32 MiB -> 389.30 MiB (-0.01%)

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

Labels

merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup 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