Displaying 3 results from an estimated 3 matches for "ismovddupmask".
2009 May 01
0
[LLVMdev] RFC: AVX Pattern Specification [LONG]
...28:$src),
"movddup\t{$src, $dst|$dst, $src}",
[(set VR128:$dst,(v2f64 (movddup VR128:$src,
(undef))))]>;
def movddup : PatFrag<(ops node:$lhs, node:$rhs),
(vector_shuffle node:$lhs, node:$rhs), [{
return X86::isMOVDDUPMask(cast<ShuffleVectorSDNode>(N));
}]>;
The goal is to replace the pattern fragment and the C++ code for
X86::isMOVDDUPMask with something like:
def movddup : PatFrag<(ops node:$lhs, node:$rhs),
(vector_shuffle node:$lhs, node:$rhs,...
2009 May 01
4
[LLVMdev] RFC: AVX Pattern Specification [LONG]
On Friday 01 May 2009 13:46, Chris Lattner wrote:
> Right, a lot of these problems can be solved by some nice refactoring
> stuff. I'm also hoping that some of the complexity in defining
> shuffle matching code can be helped by making the definition of the
> shuffle patterns more declarative within the td file. It would be
> really nice to say that "this shuffle does a
2009 May 05
2
[LLVMdev] RFC: AVX Pattern Specification [LONG]
On May 1, 2009, at 3:50 PM, Chris Lattner wrote:
>
> The goal is to replace the pattern fragment and the C++ code for
> X86::isMOVDDUPMask with something like:
>
> def movddup : PatFrag<(ops node:$lhs, node:$rhs),
> (vector_shuffle node:$lhs, node:$rhs,
> 0, 1, 0, 1, Cost<42>)
>
> Alternatively, the cost could be put on the instructions etc, whateve...