Skip to content

Upgrade halide-llvm to 22.1.8, 23.1.0rc3 - #9370

Open
halide-ci[bot] wants to merge 4 commits into
mainfrom
automated/upgrade-halide-llvm
Open

Upgrade halide-llvm to 22.1.8, 23.1.0rc3#9370
halide-ci[bot] wants to merge 4 commits into
mainfrom
automated/upgrade-halide-llvm

Conversation

@halide-ci

@halide-ci halide-ci Bot commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Automated upgrade via uv lock -P halide-llvm.

@codecov

codecov Bot commented Aug 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.95%. Comparing base (bb5426d) to head (d749003).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9370      +/-   ##
==========================================
- Coverage   70.08%   69.95%   -0.14%     
==========================================
  Files         259      260       +1     
  Lines       79158    79287     +129     
  Branches    19293    19327      +34     
==========================================
- Hits        55477    55464      -13     
- Misses      17886    17937      +51     
- Partials     5795     5886      +91     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@alexreinking alexreinking changed the title Upgrade halide-llvm to Upgrade halide-llvm to 23.1.0rc3 Aug 20, 2026
@alexreinking

Copy link
Copy Markdown
Member

Opened llvm/llvm-project#217639 to track failure here.

alexreinking and others added 2 commits August 20, 2026 11:15
…ible

LLVM 23.1's AlwaysInliner now checks target-attribute compatibility
before inlining (llvm/llvm-project#209345), and without an explicit
SME attribute a function defaults to requiring non-streaming mode.
These frecpe/frecps-based helpers are safe in either mode but had no
attribute saying so, so they stopped getting inlined into
sme_streaming() bodies, leaving standalone functions that LLVM's
AArch64 backend can't legalize:

  LLVM ERROR: Don't know how to legalize this scalable vector type

Filed upstream at llvm/llvm-project#217639
since the new inliner leaves un-inlinable IR behind instead of either
erroring cleanly or still inlining, but the missing attribute here is
the real bug: CodeGen_ARM.cpp's own dynamically-generated SVE intrinsic
wrappers already set this attribute for the same reason.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@halide-ci halide-ci Bot changed the title Upgrade halide-llvm to 23.1.0rc3 Upgrade halide-llvm to 22.1.8 Aug 21, 2026
@alexreinking alexreinking changed the title Upgrade halide-llvm to 22.1.8 Upgrade halide-llvm to 22.1.8, 23.1.0rc3 Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant