summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp
diff options
context:
space:
mode:
authorChandler Carruth <chandlerc@gmail.com>2016-03-11 13:46:00 +0000
committerChandler Carruth <chandlerc@gmail.com>2016-03-11 13:46:00 +0000
commitaef32bd319733bd233cc370e7eaf7807b5f0cade (patch)
tree275f0d859e41976b4e5f9cd1024ba4d7a7f32f0a /lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp
parent3bc9c7fb459f72009bac39ef631117e2e8b8b149 (diff)
downloadbcm5719-llvm-aef32bd319733bd233cc370e7eaf7807b5f0cade.tar.gz
bcm5719-llvm-aef32bd319733bd233cc370e7eaf7807b5f0cade.zip
[memdep] Just require domtree for memdep.
This doesn't cause us to construct dominator trees any more often in the normal pipeline, and removes an entire mode of memdep that needed to be reasoned about and maintained. Perhaps more importantly, it removes the ability for the results of memdep to be different because of accidental pass scheduling goofs or the order of evaluation of 'getResult' calls. Essentially, 'getCachedResult', unless across IR-unit boundaries, is extremely dangerous. We need to work much harder to avoid it (or its analog in the old pass manager). llvm-svn: 263232
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud