Skip to content

[LLVM] Bump to c9e8899e3 - #684

Merged
makslevental merged 2 commits into
mainfrom
update-llvm
Sep 11, 2026
Merged

makslevental merged 2 commits into
mainfrom
update-llvm

Conversation

@bump-llvm

@bump-llvm bump-llvm Bot commented Sep 8, 2026 •

Copy link
Copy Markdown
Contributor

@bump-llvm
bump-llvm Bot requested a review from makslevental September 8, 2026 01:19
@bump-llvm bump-llvm Bot changed the title [LLVM] Bump to eb74688f5 [LLVM] Bump to 4383c7f12 Sep 9, 2026
@bump-llvm
bump-llvm Bot force-pushed the update-llvm branch 2 times, most recently from a622718 to 3c890eb Compare September 10, 2026 01:18
@bump-llvm bump-llvm Bot changed the title [LLVM] Bump to 4383c7f12 [LLVM] Bump to 5524a2192 Sep 10, 2026
@bump-llvm bump-llvm Bot changed the title [LLVM] Bump to 5524a2192 [LLVM] Bump to c9e8899e3 Sep 11, 2026
The LLVM/NVVM/ROCDL "Shard generated operation definitions" changes
(llvm/llvm-project#221813, #221812, #221729) make dialect op-def sources
get sharded at build time via the mlir-src-sharder tablegen tool. That
tool must run on the host during the wasm cross-build, but it was not in
the prebuilt LLVM_NATIVE_TOOL_DIR set, so LLVM fell back to configuring
the NATIVE sub-build to produce it -- which fails under pyodide and
surfaces as the bogus "libstdc++ version must be at least 7.4".

Install mlir-src-sharder alongside the other host tools so the wasm
build resolves it from LLVM_NATIVE_TOOL_DIR and never spins up NATIVE.
@makslevental
makslevental merged commit f65b96d into main Sep 11, 2026
116 of 151 checks passed
@makslevental
makslevental deleted the update-llvm branch September 11, 2026 23:11
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