summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
diff options
context:
space:
mode:
authorTobias Grosser <tobias@grosser.es>2016-01-22 09:33:33 +0000
committerTobias Grosser <tobias@grosser.es>2016-01-22 09:33:33 +0000
commitb3a9538e9507695b5716e4d8ef3d691c9882aa86 (patch)
treeccfb176950071377f9ef21cf12e58ff249a84714 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
parent3015bcc62aa4fc948dd02736f525df4b5d18e8fb (diff)
downloadbcm5719-llvm-b3a9538e9507695b5716e4d8ef3d691c9882aa86.tar.gz
bcm5719-llvm-b3a9538e9507695b5716e4d8ef3d691c9882aa86.zip
Remove irreducible control flow from test case
The test case we look at does not necessarily require irreducible control flow, but a normal loop is sufficient to create a non-affine region containing more than one basic block that dominates the exit node. We replace this irreducible control flow with a normal loop for the following reasons: 1) This is easier to understand 2) We will subsequently commit a patch that ensures Polly does not process irreducible control flow. Within non-affine regions, we could possibly handle irreducible control flow. llvm-svn: 258496
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud