summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/breakpoint/TestBreakpointAPI.py
diff options
context:
space:
mode:
authorKyle Butt <kyle+llvm@iteratee.net>2016-10-04 23:54:18 +0000
committerKyle Butt <kyle+llvm@iteratee.net>2016-10-04 23:54:18 +0000
commitadabac2d577e0cbca61e6d0ab24098cfc1b3fe6e (patch)
tree988f376cefb60f4be05a3e6ab85583e7d1058587 /lldb/packages/Python/lldbsuite/test/python_api/breakpoint/TestBreakpointAPI.py
parent32986ede316ef75285a05eada870313a9a00c031 (diff)
downloadbcm5719-llvm-adabac2d577e0cbca61e6d0ab24098cfc1b3fe6e.tar.gz
bcm5719-llvm-adabac2d577e0cbca61e6d0ab24098cfc1b3fe6e.zip
Codegen: Tail-duplicate during placement.
The tail duplication pass uses an assumed layout when making duplication decisions. This is fine, but passes up duplication opportunities that may arise when blocks are outlined. Because we want the updated CFG to affect subsequent placement decisions, this change must occur during placement. In order to achieve this goal, TailDuplicationPass is split into a utility class, TailDuplicator, and the pass itself. The pass delegates nearly everything to the TailDuplicator object, except for looping over the blocks in a function. This allows the same code to be used for tail duplication in both places. This change, in concert with outlining optional branches, allows triangle shaped code to perform much better, esepecially when the taken/untaken branches are correlated, as it creates a second spine when the tests are small enough. Issue from previous rollback fixed, and a new test was added for that case as well. Differential revision: https://reviews.llvm.org/D18226 llvm-svn: 283274
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/breakpoint/TestBreakpointAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud