summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2018-07-03 13:44:22 +0000
committerSanjay Patel <spatel@rotateright.com>2018-07-03 13:44:22 +0000
commit3074b9e53f46f7ea398b34c325553dcccf02607a (patch)
treee3ab572ec741b29695e26be1fcbebb03bc52e33b /lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py
parentffc1681620881901eb064046234e61b0ea4a6df4 (diff)
downloadbcm5719-llvm-3074b9e53f46f7ea398b34c325553dcccf02607a.tar.gz
bcm5719-llvm-3074b9e53f46f7ea398b34c325553dcccf02607a.zip
[InstCombine] fold shuffle-with-binop and common value
This is the last significant change suggested in PR37806: https://bugs.llvm.org/show_bug.cgi?id=37806#c5 ...though there are several follow-ups noted in the code comments in this patch to complete this transform. It's possible that a binop feeding a select-shuffle has been eliminated by earlier transforms (or the code was just written like this in the 1st place), so we'll fail to match the patterns that have 2 binops from: D48401, D48678, D48662, D48485. In that case, we can try to materialize identity constants for the remaining binop to fill in the "ghost" lanes of the vector (where we just want to pass through the original values of the source operand). I added comments to ConstantExpr::getBinOpIdentity() to show planned follow-ups. For now, we only handle the 5 commutative integer binops (add/mul/and/or/xor). Differential Revision: https://reviews.llvm.org/D48830 llvm-svn: 336196
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/target/TestTargetAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud