aboutsummaryrefslogtreecommitdiff
path: root/llvm/unittests/ExecutionEngine/Orc/ObjectFormatsTest.cpp
diff options
context:
space:
mode:
authorFlorian Hahn <flo@fhahn.com>2025-10-14 20:18:39 +0100
committerGitHub <noreply@github.com>2025-10-14 19:18:39 +0000
commit3b46556cb7034409a4bb2566c6d0df7620c56bba (patch)
tree6ea3889caf138250cc0759b5a6664098671726f6 /llvm/unittests/ExecutionEngine/Orc/ObjectFormatsTest.cpp
parent6a7754f2acd19a8045073f7aaadc8d78fc219c7c (diff)
downloadllvm-3b46556cb7034409a4bb2566c6d0df7620c56bba.zip
llvm-3b46556cb7034409a4bb2566c6d0df7620c56bba.tar.gz
llvm-3b46556cb7034409a4bb2566c6d0df7620c56bba.tar.bz2
[SCEV] Use context instruction for SCEVUnknowns in getConstantMultiple. (#163260)
Follow-up to https://github.com/llvm/llvm-project/pull/160941. Even if we don't have a context instruction for the caller, we should be able to provide context instructions for SCEVUnknowns. Unless I am missing something, SCEVUnknown only become available at the point their underlying IR instruction has been defined. If it is an argument, it should be safe to use the first instruction in the entry block or the instruction itself if it wraps an instruction. This allows getConstantMultiple to make better use of alignment assumptions. PR: https://github.com/llvm/llvm-project/pull/163260
Diffstat (limited to 'llvm/unittests/ExecutionEngine/Orc/ObjectFormatsTest.cpp')
0 files changed, 0 insertions, 0 deletions