summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/process/TestProcessAPI.py
diff options
context:
space:
mode:
authorHans Wennborg <hans@hanshq.net>2019-08-12 14:23:13 +0000
committerHans Wennborg <hans@hanshq.net>2019-08-12 14:23:13 +0000
commita45f301f7a5d0f62910d0ed93c96d221555697c9 (patch)
tree41fa455129e4bddd79433bca19e28dc6e27b844e /lldb/packages/Python/lldbsuite/test/python_api/process/TestProcessAPI.py
parente011a5b4edf828dcaaa4ab5552b71d2bacaaecab (diff)
downloadbcm5719-llvm-a45f301f7a5d0f62910d0ed93c96d221555697c9.tar.gz
bcm5719-llvm-a45f301f7a5d0f62910d0ed93c96d221555697c9.zip
Revert r368339 "[MBP] Disable aggressive loop rotate in plain mode"
It caused assertions to fire when building Chromium: lib/CodeGen/LiveDebugValues.cpp:331: bool {anonymous}::LiveDebugValues::OpenRangesSet::empty() const: Assertion `Vars.empty() == VarLocs.empty() && "open ranges are inconsistent"' failed. See https://crbug.com/992871#c3 for how to reproduce. > Patch https://reviews.llvm.org/D43256 introduced more aggressive loop layout optimization which depends on profile information. If profile information is not available, the statically estimated profile information(generated by BranchProbabilityInfo.cpp) is used. If user program doesn't behave as BranchProbabilityInfo.cpp expected, the layout may be worse. > > To be conservative this patch restores the original layout algorithm in plain mode. But user can still try the aggressive layout optimization with -force-precise-rotation-cost=true. > > Differential Revision: https://reviews.llvm.org/D65673 llvm-svn: 368579
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/process/TestProcessAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud