aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectBreakpointCommand.cpp
diff options
context:
space:
mode:
authorJuergen Ributzka <juergen@apple.com>2014-08-27 22:52:33 +0000
committerJuergen Ributzka <juergen@apple.com>2014-08-27 22:52:33 +0000
commitad8beabe38f5d1f2045ba91940877639ba46e7c0 (patch)
tree7e7ea1fa1bf96a64d4016d391fcd0d095911780d /lldb/source/Commands/CommandObjectBreakpointCommand.cpp
parent5971e8c2dbdd27329be5cf61bc59fa9e67e1f7cb (diff)
downloadllvm-ad8beabe38f5d1f2045ba91940877639ba46e7c0.zip
llvm-ad8beabe38f5d1f2045ba91940877639ba46e7c0.tar.gz
llvm-ad8beabe38f5d1f2045ba91940877639ba46e7c0.tar.bz2
[FastISel][AArch64] Don't fold instructions too aggressively into the memory operation.
Currently instructions are folded very aggressively into the memory operation, which can lead to the use of killed operands: %vreg1<def> = ADDXri %vreg0<kill>, 2 %vreg2<def> = LDRBBui %vreg0, 2 ... = ... %vreg1 ... This usually happens when the result is also used by another non-memory instruction in the same basic block, or any instruction in another basic block. If the computed address is used by only memory operations in the same basic block, then it is safe to fold them. This is because all memory operations will fold the address computation and the original computation will never be emitted. This fixes rdar://problem/18142857. llvm-svn: 216629
Diffstat (limited to 'lldb/source/Commands/CommandObjectBreakpointCommand.cpp')
0 files changed, 0 insertions, 0 deletions