summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python/modify-python-lldb.py
diff options
context:
space:
mode:
authorBjorn Pettersson <bjorn.a.pettersson@ericsson.com>2019-04-23 10:01:08 +0000
committerBjorn Pettersson <bjorn.a.pettersson@ericsson.com>2019-04-23 10:01:08 +0000
commitf97b29be884c19dab24ccdfc2e9c81be970953bc (patch)
treedc3eb4a58894f528c3d8c3a02f1b04409b71cd22 /lldb/scripts/Python/modify-python-lldb.py
parent2359429168a8f8882cd9caaac7c4e24803fabbb8 (diff)
downloadbcm5719-llvm-f97b29be884c19dab24ccdfc2e9c81be970953bc.tar.gz
bcm5719-llvm-f97b29be884c19dab24ccdfc2e9c81be970953bc.zip
[DAGCombiner] Combine OR as ADD when no common bits are set
Summary: The DAGCombiner is rewriting (canonicalizing) an ISD::ADD with no common bits set in the operands as an ISD::OR node. This could sometimes result in "missing out" on some combines that normally are performed for ADD. To be more specific this could happen if we already have rewritten an ADD into OR, and later (after legalizations or combines) we expose patterns that could have been optimized if we had seen the OR as an ADD (e.g. reassociations based on ADD). To make the DAG combiner less sensitive to if ADD or OR is used for these "no common bits set" ADD/OR operations we now apply most of the ADD combines also to an OR operation, when value tracking indicates that the operands have no common bits set. Reviewers: spatel, RKSimon, craig.topper, kparzysz Reviewed By: spatel Subscribers: arsenm, rampitec, lebedev.ri, jvesely, nhaehnle, hiraditya, javed.absar, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D59758 llvm-svn: 358965
Diffstat (limited to 'lldb/scripts/Python/modify-python-lldb.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud