Skip to content

Conversation

@j2kun
Copy link
Contributor

@j2kun j2kun commented Mar 31, 2025

MacOS platforms using mlir-runner in lit tests consistently hit the following error:

# .---command stderr------------
# | JIT session error: Symbols not found: [ __mlir_ciface_printMemrefI32 ]
# | Error: Failed to materialize symbols: { (main, { __mlir_printMemrefI32, ... }) }
# `-----------------------------

google/heir#1521 (comment) confirms the issue is fixed by using alwayslink on these two targets, and I confirmed on a separate Apple M1 (OSX version Sequoia 15.3.2.).

I'm not an expert on the mlir runner internals, but given the mlir-runner is purely for testing, and alwayslink at worst adds some overhead by not removing symbols, it seems low risk.

@llvmbot llvmbot added the bazel "Peripheral" support tier build system: utils/bazel label Mar 31, 2025
@j2kun j2kun merged commit 179062b into llvm:main Apr 1, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bazel "Peripheral" support tier build system: utils/bazel

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants