summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/signals/main.cpp
diff options
context:
space:
mode:
authorJames Y Knight <jyknight@google.com>2015-11-02 18:48:08 +0000
committerJames Y Knight <jyknight@google.com>2015-11-02 18:48:08 +0000
commit646c4032e7e9634ad102a00987fa92c1c5bacd5a (patch)
tree74859a861baf7e3560b726411b74071e9be710cf /lldb/packages/Python/lldbsuite/test/python_api/signals/main.cpp
parent06fb04f1fa22b2d2398e3c426a204484fd524919 (diff)
downloadbcm5719-llvm-646c4032e7e9634ad102a00987fa92c1c5bacd5a.tar.gz
bcm5719-llvm-646c4032e7e9634ad102a00987fa92c1c5bacd5a.zip
Fix two issues in MergeConsecutiveStores:
1) PR25154. This is basically a repeat of PR18102, which was fixed in r200201, and broken again by r234430. The latter changed which of the store nodes was merged into from the first to the last. Thus, we now also need to prefer merging a later store at a given address into the target node, instead of an earlier one. 2) While investigating that, I also realized I'd introduced a bug in r236850. There, I removed a check for alignment -- not realizing that nothing except the alignment check was ensuring that none of the stores were overlapping! This is a really bogus way to ensure there's no aliased stores. A better solution to both of these issues is likely to always use the code added in the 'if (UseAA)' branches which rearrange the chain based on a more principled analysis. I'll look into whether that can be used always, but in the interest of getting things back to working, I think a minimal change makes sense. llvm-svn: 251816
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud