summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
diff options
context:
space:
mode:
authorHiroshi Inoue <inouehrs@jp.ibm.com>2018-06-07 13:21:14 +0000
committerHiroshi Inoue <inouehrs@jp.ibm.com>2018-06-07 13:21:14 +0000
commit01ef4c2c64e17f339d1ef9da992493c652be7f8e (patch)
treebaebfc4d2d39f1caf4684caeb48a79522779ac9a /lldb/packages/Python/lldbsuite/test/python_api
parent241f286bd731e40c89883cf70ecf0961aae32cd3 (diff)
downloadbcm5719-llvm-01ef4c2c64e17f339d1ef9da992493c652be7f8e.tar.gz
bcm5719-llvm-01ef4c2c64e17f339d1ef9da992493c652be7f8e.zip
[PowerPC] avoid unprofitable Repl32 flag in BitPermutationSelector
BitPermutationSelector sets Repl32 flag for bit groups which can be (potentially) benefit from 32-bit rotate-and-mask instructions with bit replication, i.e. rlwinm/rlwimi copies lower 32 bits into upper 32 bits on 64-bit PowerPC before rotation. However, enforcing 32-bit instruction sometimes results in redundant generated code. For example, the following simple code is compiled into rotldi + rlwimi while it can be compiled into only rldimi instruction if Repl32 flag is not set on the bit group for (a & 0xFFFFFFFF). uint64_t func(uint64_t a, uint64_t b) { return (a & 0xFFFFFFFF) | (b << 32) ; } To avoid such problem, this patch checks the potential benefit of Repl32 flag before setting it. If a bit group does not require rotation (i.e. RLAmt == 0) and won't be merged into another group, we do not benefit from Repl32 flag on this group. Differential Revision: https://reviews.llvm.org/D47867 llvm-svn: 334195
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud