Skip to content

Upgrade halide-llvm to 23.0.0.dev91651+g37e0109a#9118

Merged
abadams merged 2 commits intomainfrom
automated/upgrade-halide-llvm
May 4, 2026
Merged

Upgrade halide-llvm to 23.0.0.dev91651+g37e0109a#9118
abadams merged 2 commits intomainfrom
automated/upgrade-halide-llvm

Conversation

@halide-ci
Copy link
Copy Markdown
Contributor

@halide-ci halide-ci Bot commented May 3, 2026

Automated upgrade via uv lock -P halide-llvm.

@alexreinking
Copy link
Copy Markdown
Member

@copilot can you please fix the build error arising from the LLVM version upgrade? Change the code to use the new APIs, gated appropriately by version-checking preprocessor directives to maintain compatibility with older major versions.

…ager

Agent-Logs-Url: https://github.com/halide/Halide/sessions/89bc7b2b-c03a-43c0-980f-f33e13ed2708

Co-authored-by: alexreinking <169273+alexreinking@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

Copilot AI commented May 3, 2026

@copilot can you please fix the build error arising from the LLVM version upgrade? Change the code to use the new APIs, gated appropriately by version-checking preprocessor directives to maintain comp...

Fixed in b0cfaa3. The linkerBuilder lambda for ObjectLinkingLayer already had the JITLinkMemoryManager& parameter in the LLVM 23 signature but it was anonymous and unused. In LLVM 23, the single-argument ObjectLinkingLayer(ExecutionSession&) constructor was removed and a memory manager is now required. The fix names the parameter memMgr and passes it to the constructor under #if LLVM_VERSION >= 230, preserving the old behavior for older LLVM versions.

Copilot AI requested a review from alexreinking May 3, 2026 13:08
@abadams abadams merged commit 3a85d79 into main May 4, 2026
22 of 24 checks passed
@halide-ci halide-ci Bot deleted the automated/upgrade-halide-llvm branch May 5, 2026 06:52
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.

3 participants