aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
diff options
context:
space:
mode:
authorNikita Popov <npopov@redhat.com>2025-02-12 10:14:00 +0100
committerGitHub <noreply@github.com>2025-02-12 10:14:00 +0100
commitc03325cead2244ef0a89bb1cf365bddf16021daf (patch)
tree56f8015d9f123c5ced5f6f9aca4838e2c10468b9 /lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
parent8359dbc8c08ca4206534d605dd299713dc323b67 (diff)
downloadllvm-c03325cead2244ef0a89bb1cf365bddf16021daf.zip
llvm-c03325cead2244ef0a89bb1cf365bddf16021daf.tar.gz
llvm-c03325cead2244ef0a89bb1cf365bddf16021daf.tar.bz2
[MLIR][LLVMIR] Use TargetFolder when creating globals (#126745)
The LLVM dialect lowers globals using IRBuilder, relying on it creating constant expressions where possible. As we remove support for more constant expressions (per https://discourse.llvm.org/t/rfc-remove-most-constant-expressions/63179), this can cause issues for cases where the constant expression is no longer supported, and the operation cannot be constant folded without DataLayout being available. In particular, I ran into this issue with flang and the removal of mul constant expressions. Address this by using TargetFolder when creating globals, which will perform DL-aware constant folding. I think it would make sense to also do this in general, but I'm starting with globals where not doing this can result in translation failures. Ideally, globals with these problematic expressions would never be generated in the first place, but there has been little movement on fixing this (https://github.com/llvm/llvm-project/issues/96047).
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h')
0 files changed, 0 insertions, 0 deletions