summaryrefslogtreecommitdiffstats
path: root/lldb/source/Expression/IRInterpreter.cpp
diff options
context:
space:
mode:
authorJakob Stoklund Olesen <stoklund@2pi.dk>2012-01-11 02:07:05 +0000
committerJakob Stoklund Olesen <stoklund@2pi.dk>2012-01-11 02:07:05 +0000
commit8b1d023a4aec842d90074684048b10cbfb014536 (patch)
treefca0b92625a1c33a6d07ee988bade3bc60e435e3 /lldb/source/Expression/IRInterpreter.cpp
parent67aec124091659f4e43fb0be67c07bb060763c19 (diff)
downloadbcm5719-llvm-8b1d023a4aec842d90074684048b10cbfb014536.tar.gz
bcm5719-llvm-8b1d023a4aec842d90074684048b10cbfb014536.zip
Detect when a value is undefined on an edge to a landing pad.
Consider this code: int h() { int x; try { x = f(); g(); } catch (...) { return x+1; } return x; } The variable x is undefined on the first edge to the landing pad, but it has the f() return value on the second edge to the landing pad. SplitAnalysis::getLastSplitPoint() would assume that the return value from f() was live into the landing pad when f() throws, which is of course impossible. Detect these cases, and treat them as if the landing pad wasn't there. This allows spill code to be inserted after the function call to f(). <rdar://problem/10664933> llvm-svn: 147912
Diffstat (limited to 'lldb/source/Expression/IRInterpreter.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud