Skip to content

Conversation

GuillaumeGomez
Copy link
Member

@GuillaumeGomez GuillaumeGomez commented Oct 13, 2025

Successful merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

Kobzol and others added 21 commits October 6, 2025 09:35
Note that the code in `LLVMRustDIBuilderCreateStaticVariable` that tried to
downcast `InitVal` appears to have been dead, because `llvm::ConstantInt` and
`llvm::ConstantFP` are not subclasses of `llvm::GlobalVariable`.
…-normalize, r=lcnr

repr_transparent_external_private_fields: normalize types during traversal

Determining whether a type is a 1-ZST will internally do full normalization, so we better do the same when scanning for non-exhaustive types.

r? ``@lcnr``
…mulacrum

Add doc links between `{integer}::from_str_radix` and `from_str`

When parsing base-10 numbers, it's easy to miss `<Self as FromStr>::from_str` and `str::parse` as potential alternatives to `from_str_radix`.

- A similar suggestion is given by https://rust-lang.github.io/rust-clippy/master/index.html#from_str_radix_10
cg_llvm: Use `LLVMDIBuilderCreateGlobalVariableExpression`

- Part of rust-lang#134001
- Follow-up to rust-lang#146763

---

This PR dismantles the somewhat complicated `LLVMRustDIBuilderCreateStaticVariable` function, and replaces it with equivalent calls to `LLVMDIBuilderCreateGlobalVariableExpression` and `LLVMGlobalSetMetadata`.

A key difference is that the new code does not replicate the attempted downcast of `InitVal`. As far as I can tell, those downcasts were actually dead, because `llvm::ConstantInt` and `llvm::ConstantFP` are not subclasses of `llvm::GlobalVariable`. I tried replacing those code paths with fatal errors, and was unable to induce failure in any of the relevant test suites I ran.

I have also confirmed that if the calls to `create_static_variable` are commented out, debuginfo tests will fail, demonstrating some amount of relevant test coverage.

The new `DIBuilder` methods have been added via an extension trait, not as inherent methods, to avoid impeding rust-lang#142897.
Clear `ChunkedBitSet` without reallocating

There doesn't appear to be any reason to clear a ChunkedBitSet via its constructor (which allocates a new list of chunks), when we could just fill the existing allocation with `Chunk::Zeros` instead.

For comparison, the `insert_all` impl added by the same PR (rust-lang#93984) does the simple thing here and just overwrites every chunk with `Chunk::Ones`.

(That fill was then made somewhat easier by rust-lang#145480, which removes the chunk size from all-zero/all-one chunks.)

r? nnethercote (or compiler)
Generalize configuring LLD as the default linker in bootstrap

Reopen of rust-lang#147157, because apparently bors can't deal with it for some reason.

r? ``@ghost``
@rustbot rustbot added A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. A-testsuite Area: The testsuite used to check the correctness of rustc 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. rollup A PR which is a rollup labels Oct 13, 2025
@GuillaumeGomez
Copy link
Member Author

@bors r+ p=5 rollup=never

@bors
Copy link
Collaborator

bors commented Oct 13, 2025

📌 Commit 0e6ec72 has been approved by GuillaumeGomez

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 Oct 13, 2025
@bors
Copy link
Collaborator

bors commented Oct 13, 2025

⌛ Testing commit 0e6ec72 with merge 9b82646...

@bors
Copy link
Collaborator

bors commented Oct 13, 2025

☀️ Test successful - checks-actions
Approved by: GuillaumeGomez
Pushing 9b82646 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Oct 13, 2025
@bors bors merged commit 9b82646 into rust-lang:master Oct 13, 2025
11 checks passed
@rustbot rustbot added this to the 1.92.0 milestone Oct 13, 2025
@rust-timer
Copy link
Collaborator

📌 Perf builds for each rolled up PR:

PR# Message Perf Build Sha
#147514 repr_transparent_external_private_fields: normalize types d… f6ec643da501608f25dae9270046e59b6ed6949d (link)
#147605 Add doc links between {integer}::from_str_radix and `from… ea0a8fff77bae1303949e03b317d46053b7c02db (link)
#147608 cg_llvm: Use LLVMDIBuilderCreateGlobalVariableExpression a0ff00ecb620202ac920e9b4da489873e5a26b60 (link)
#147623 Clear ChunkedBitSet without reallocating 8e73ac269b89e201d9f8078fb0a96504ef479571 (link)
#147625 Add a warning when running tests with the GCC backend and d… 514fdd0323104856df570c24752e02a01a3e8789 (link)
#147626 Generalize configuring LLD as the default linker in bootstr… a68f179a9509e7d496014b070d2555adea815065 (link)

previous master: 956f47c32f

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 956f47c (parent) -> 9b82646 (this PR)

Test differences

Show 387 test diffs

Stage 0

  • core::builder::tests::snapshot::build_compiler_lld_opt_in_lld_disabled: [missing] -> pass (J0)

Additionally, 386 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 9b8264604ef800b5539d04bf78ebdef5c5fa4968 --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: 5878.1s -> 7659.5s (30.3%)
  2. dist-x86_64-apple: 8213.0s -> 6792.5s (-17.3%)
  3. aarch64-msvc-2: 5269.8s -> 4636.4s (-12.0%)
  4. dist-aarch64-msvc: 5614.1s -> 6278.6s (11.8%)
  5. x86_64-gnu-llvm-20: 2547.3s -> 2845.0s (11.7%)
  6. dist-arm-linux-gnueabi: 4910.8s -> 5419.1s (10.4%)
  7. x86_64-gnu-miri: 4331.3s -> 4775.5s (10.3%)
  8. aarch64-gnu: 7197.2s -> 6473.3s (-10.1%)
  9. dist-aarch64-linux: 6616.2s -> 6011.7s (-9.1%)
  10. aarch64-gnu-llvm-20-1: 3583.8s -> 3886.8s (8.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 (9b82646): 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.1% [0.1%, 0.1%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary 3.1%, secondary -1.5%)

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

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

Cycles

Results (secondary 0.3%)

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.3% [2.2%, 4.1%] 4
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-3.7% [-5.6%, -2.6%] 3
All ❌✅ (primary) - - 0

Binary size

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

Bootstrap: 474.655s -> 474.96s (0.06%)
Artifact size: 388.12 MiB -> 388.14 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-testsuite Area: The testsuite used to check the correctness of rustc 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants