summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/process/TestProcessAPI.py
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2019-01-22 14:24:13 +0000
committerSanjay Patel <spatel@rotateright.com>2019-01-22 14:24:13 +0000
commiteffee52c59a0716980d545a97ab61d0c9839660a (patch)
tree4c44e74681a39c4502d74e00970abc0518cb5a24 /lldb/packages/Python/lldbsuite/test/python_api/process/TestProcessAPI.py
parent121fcd7ec6ad051750cb56756d7895f12783802e (diff)
downloadbcm5719-llvm-effee52c59a0716980d545a97ab61d0c9839660a.tar.gz
bcm5719-llvm-effee52c59a0716980d545a97ab61d0c9839660a.zip
[DAGCombiner] narrow vector binop with 2 insert subvector operands
vecbo (insertsubv undef, X, Z), (insertsubv undef, Y, Z) --> insertsubv VecC, (vecbo X, Y), Z This is another step in generic vector narrowing. It's also a step towards more horizontal op formation specifically for x86 (although we still failed to match those in the affected tests). The scalarization cases are also not optimal (we should be scalarizing those), but it's still an improvement to use a narrower vector op when we know part of the result must be constant because both inputs are undef in some vector lanes. I think a similar match but checking for a constant operand might help some of the cases in D51553. Differential Revision: https://reviews.llvm.org/D56875 llvm-svn: 351825
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/process/TestProcessAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud