aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/lldbgdbclient.py
diff options
context:
space:
mode:
authorBjörn Pettersson <bjorn.a.pettersson@ericsson.com>2025-06-25 09:30:26 +0200
committerGitHub <noreply@github.com>2025-06-25 09:30:26 +0200
commit237b8de2c0d9ee50c6a744e95c0706c8cdea70e1 (patch)
treec51c008061be5e6175b6ee29440e49eccfa34fe5 /lldb/packages/Python/lldbsuite/test/lldbgdbclient.py
parent7c38ee26d44124c93dc1553cde36837928c96d41 (diff)
downloadllvm-237b8de2c0d9ee50c6a744e95c0706c8cdea70e1.zip
llvm-237b8de2c0d9ee50c6a744e95c0706c8cdea70e1.tar.gz
llvm-237b8de2c0d9ee50c6a744e95c0706c8cdea70e1.tar.bz2
[IfConversion] Fix bug related to !HasFallThrough (#145471)
We can not trust that !HasFallThrough implies that there is not fallthrough exit in cases when analyzeBranch failed. Adding a new blockNeverFallThrough helper to make the tests on !HasFallThrough safe by also checking IsBrAnalyzable. We also try to prove no-fallthrough by inspecting the successor list. If the textual successor isn't in the successor list we know that there is no fallthrough. The bug has probably been around for years. Found it when working on an out-of-tree target.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbgdbclient.py')
0 files changed, 0 insertions, 0 deletions