aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/IR/Module.cpp
diff options
context:
space:
mode:
authorJeremy Morse <jeremy.morse@sony.com>2021-07-28 15:37:09 +0100
committerJeremy Morse <jeremy.morse@sony.com>2021-07-28 15:56:00 +0100
commit8612417e5a54cfef941ab45de55e48b4a0c4e8b4 (patch)
tree97d577541465b7d228ddaf06b8b2b8b4751d8c57 /llvm/lib/IR/Module.cpp
parent66ddac22e2a7f268e91c26d694112970dfa607ae (diff)
downloadllvm-8612417e5a54cfef941ab45de55e48b4a0c4e8b4.zip
llvm-8612417e5a54cfef941ab45de55e48b4a0c4e8b4.tar.gz
llvm-8612417e5a54cfef941ab45de55e48b4a0c4e8b4.tar.bz2
[DebugInfo][InstrRef] Don't break up ret-sequences on debug-info instrs
When we have a terminator sequence (i.e. a tailcall or return), MIIsInTerminatorSequence is used to work out where the preceding ABI-setup instructions end, i.e. the parts that were glued to the terminator instruction. This allows LLVM to split blocks safely without having to worry about ABI stuff. The function only ignores DBG_VALUE instructions, meaning that the two debug instructions I recently added can end terminator sequences early, causing various MachineVerifier errors. This patch promotes the test for debug instructions from "isDebugValue" to "isDebugInstr", thus avoiding any debug-info interfering with this function. Differential Revision: https://reviews.llvm.org/D106660
Diffstat (limited to 'llvm/lib/IR/Module.cpp')
0 files changed, 0 insertions, 0 deletions