summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/dotest.py
diff options
context:
space:
mode:
authorJustin Bogner <mail@justinbogner.com>2015-12-15 19:40:57 +0000
committerJustin Bogner <mail@justinbogner.com>2015-12-15 19:40:57 +0000
commit843fb204b7102bc1abd7fdadf39f3ac2e0acb479 (patch)
tree911cfa2d243582a779de1e1edffbc4a01045d384 /lldb/packages/Python/lldbsuite/test/dotest.py
parent33beb24318f9e5355f1aa481cddcbb50eaf2a156 (diff)
downloadbcm5719-llvm-843fb204b7102bc1abd7fdadf39f3ac2e0acb479.tar.gz
bcm5719-llvm-843fb204b7102bc1abd7fdadf39f3ac2e0acb479.zip
LPM: Stop threading `Pass *` through all of the loop utility APIs. NFC
A large number of loop utility functions take a `Pass *` and reach into it to find out which analyses to preserve. There are a number of problems with this: - The APIs have access to pretty well any Pass state they want, so it's hard to tell what they may or may not do. - Other APIs have copied these and pass around a `Pass *` even though they don't even use it. Some of these just hand a nullptr to the API since the callers don't even have a pass available. - Passes in the new pass manager don't work like the current ones, so the APIs can't be used as is there. Instead, we should explicitly thread the analysis results that we actually care about through these APIs. This is both simpler and more reusable. llvm-svn: 255669
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/dotest.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud