summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2016-07-13 18:07:02 +0000
committerSanjay Patel <spatel@rotateright.com>2016-07-13 18:07:02 +0000
commitc00e48a3db8d7694612c3a358a9017bc79f2f782 (patch)
tree1f098e6f3ca295e1e00fdec788767648fcef0b04 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
parent0532c190f7b0a8c33fdc20485c23815e2321bd16 (diff)
downloadbcm5719-llvm-c00e48a3db8d7694612c3a358a9017bc79f2f782.tar.gz
bcm5719-llvm-c00e48a3db8d7694612c3a358a9017bc79f2f782.zip
[InstCombine] extend vector select matching for non-splat constants
In D21740, we discussed trying to make this a more general matcher. However, I didn't see a clean way to handle the regular m_Not cases and these non-splat vector patterns, so I've opted for the direct approach here. If there are other potential uses of areInverseVectorBitmasks(), we could move that helper function to a higher level. There is an open question as to which is of these forms should be considered the canonical IR: %sel = select <4 x i1> <i1 true, i1 false, i1 false, i1 true>, <4 x i32> %a, <4 x i32> %b %shuf = shufflevector <4 x i32> %a, <4 x i32> %b, <4 x i32> <i32 0, i32 5, i32 6, i32 3> Differential Revision: http://reviews.llvm.org/D22114 llvm-svn: 275289
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud