aboutsummaryrefslogtreecommitdiff
path: root/lldb/unittests/ScriptInterpreter/Python
diff options
context:
space:
mode:
authorJeremy Kun <jkun@google.com>2025-04-01 08:58:32 -0700
committerGitHub <noreply@github.com>2025-04-01 08:58:32 -0700
commit179062b2dc9405a81cf44dbe676817806a4e7c6a (patch)
treede9ad408db56b0c79c9b899140dd2400b03500fb /lldb/unittests/ScriptInterpreter/Python
parenta03fce4e200d47b9133897b8f0d4688b30b42689 (diff)
downloadllvm-179062b2dc9405a81cf44dbe676817806a4e7c6a.zip
llvm-179062b2dc9405a81cf44dbe676817806a4e7c6a.tar.gz
llvm-179062b2dc9405a81cf44dbe676817806a4e7c6a.tar.bz2
[mlir][bazel] add alwayslink=True to mlir-runner utils (#133787)
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, ... }) } # `----------------------------- ``` https://github.com/google/heir/issues/1521#issuecomment-2751303404 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.
Diffstat (limited to 'lldb/unittests/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions