summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lldbutil.py
diff options
context:
space:
mode:
authorAdam Nemet <anemet@apple.com>2016-12-01 17:34:50 +0000
committerAdam Nemet <anemet@apple.com>2016-12-01 17:34:50 +0000
commit4ddb8c01b1b3c1cb24e87f992ad00826025ac1ba (patch)
tree4a4fc941e79d25f8b2551481bb7f4c8a7d9920d7 /lldb/packages/Python/lldbsuite/test/lldbutil.py
parent8b5fba8081d1494b367671095c6d74d0a013694f (diff)
downloadbcm5719-llvm-4ddb8c01b1b3c1cb24e87f992ad00826025ac1ba.tar.gz
bcm5719-llvm-4ddb8c01b1b3c1cb24e87f992ad00826025ac1ba.zip
[GVN, OptDiag] Print the interesting instructions involved in missed load-elimination
[recommitting after the fix in r288307] This includes the intervening store and the load/store that we're trying to forward from in the optimization remark for the missed load elimination. This is hooked up under a new mode in ORE that allows for compile-time budget for a bit more analysis to print more insightful messages. This mode is currently enabled for -fsave-optimization-record (-Rpass is trickier since it is controlled in the front-end). With this we can now print the red remark in http://lab.llvm.org:8080/artifacts/opt-view_test-suite/build/SingleSource/Benchmarks/Dhrystone/CMakeFiles/dry.dir/html/_org_test-suite_SingleSource_Benchmarks_Dhrystone_dry.c.html#L446 Differential Revision: https://reviews.llvm.org/D26490 llvm-svn: 288381
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbutil.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud