Skip to content

Update LLVM to 22.1.0#153066

Merged
rust-bors[bot] merged 1 commit intorust-lang:mainfrom
dianqk:update-llvm
Feb 25, 2026
Merged

Update LLVM to 22.1.0#153066
rust-bors[bot] merged 1 commit intorust-lang:mainfrom
dianqk:update-llvm

Conversation

@dianqk
Copy link
Member

@dianqk dianqk commented Feb 24, 2026

Fixes #151813.
Fixes #151946.

@rustbot rustbot added 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. labels Feb 24, 2026
@rustbot
Copy link
Collaborator

rustbot commented Feb 24, 2026

r? @cuviper

rustbot has assigned @cuviper.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: @cuviper

@rustbot
Copy link
Collaborator

rustbot commented Feb 24, 2026

⚠️ Warning ⚠️

@cuviper
Copy link
Member

cuviper commented Feb 24, 2026

@bors r+ rollup=never p=1

@rust-bors
Copy link
Contributor

rust-bors bot commented Feb 24, 2026

📌 Commit a8e76b9 has been approved by cuviper

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 Feb 24, 2026
@JonathanBrouwer
Copy link
Contributor

JonathanBrouwer commented Feb 25, 2026

@bors p=6
Scheduling this before the next rollup

@rust-bors

This comment has been minimized.

rust-bors bot pushed a commit that referenced this pull request Feb 25, 2026
@JonathanBrouwer
Copy link
Contributor

Seems to be stuck building LLVM, probably because the caches being reset because this is an LLVM upgrade.
Let's keep this running so we can get as much stuff into cache as possible

@JonathanBrouwer
Copy link
Contributor

JonathanBrouwer commented Feb 25, 2026

6 hours have passed
@bors cancel
Lets retry immediately

@rust-bors
Copy link
Contributor

rust-bors bot commented Feb 25, 2026

Auto build cancelled. Cancelled workflows:

The next pull request likely to be tested is #153066.

@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 Feb 25, 2026
@rust-bors
Copy link
Contributor

rust-bors bot commented Feb 25, 2026

☀️ Test successful - CI
Approved by: cuviper
Duration: 4h 1m 35s
Pushing 1ed4882 to main...

@rust-bors rust-bors bot merged commit 1ed4882 into rust-lang:main Feb 25, 2026
12 checks passed
@rustbot rustbot added this to the 1.95.0 milestone Feb 25, 2026
@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 3f98535 (parent) -> 1ed4882 (this PR)

Test differences

Show 1 test diff

Stage 2

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

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 1ed488274bec5bf5cfe6bf7a1cc089abcc4ebd68 --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. pr-check-1: 27m 5s -> 41m 29s (+53.2%)
  2. pr-check-2: 37m 31s -> 54m 44s (+45.9%)
  3. x86_64-rust-for-linux: 45m 48s -> 1h 3m (+37.8%)
  4. dist-aarch64-linux: 1h 50m -> 2h 28m (+35.2%)
  5. x86_64-gnu-stable: 2h 3m -> 2h 39m (+29.1%)
  6. x86_64-gnu-tools: 56m 55s -> 1h 12m (+27.0%)
  7. x86_64-gnu-gcc: 1h 2m -> 1h 16m (+23.3%)
  8. x86_64-gnu-miri: 1h 14m -> 1h 31m (+23.1%)
  9. arm-android: 1h 37m -> 1h 59m (+23.0%)
  10. x86_64-gnu-nopt: 2h 25m -> 2h 58m (+22.7%)
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 (1ed4882): 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.1%, -0.1%] 1
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary 6.2%, secondary -7.7%)

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

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

Cycles

Results (secondary 10.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)
10.3% [2.7%, 17.8%] 2
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) - - 0

Binary size

Results (primary 0.0%, secondary 0.0%)

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

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

Bootstrap: 480.701s -> 492.161s (2.38%)
Artifact size: 397.77 MiB -> 395.78 MiB (-0.50%)

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. merged-by-bors This PR was explicitly merged by bors.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

unsafe(naked) functions might not be called via a thunk rustc on SPARC miscompiled after LLVM 22 update

5 participants