Displaying 4 results from an estimated 4 matches for "immallonesv".
2020 Feb 19
2
i1 true ^= -1 in DAG matcher?
The vnot PatFrag uses ImmAllOnesV which should put an OPC_CheckImmAllOnesV
in the matcher table. And the matcher table should call
ISD::isBuildVectorAllOnes. I believe we use vnot with vXi1 vectors on X86
and I haven't seen any issues.
The FIXME you pointed to seems related to a scalar patcher not a vector
pattern. In that cas...
2020 Feb 19
2
i1 true ^= -1 in DAG matcher?
...of those two
> vectors. I would have expected a vector of 1, not -1. I would love to send
> in a better open source reproducer, will try to construct one.
>
> On Wed, Feb 19, 2020 at 11:30 AM Craig Topper <craig.topper at gmail.com>
> wrote:
>
>> The vnot PatFrag uses ImmAllOnesV which should put
>> an OPC_CheckImmAllOnesV in the matcher table. And the matcher table should
>> call ISD::isBuildVectorAllOnes. I believe we use vnot with vXi1 vectors on
>> X86 and I haven't seen any issues.
>>
>> The FIXME you pointed to seems related to a scal...
2020 Feb 19
2
i1 true ^= -1 in DAG matcher?
Hello,
It looks like that in the DAG matcher, the DAG has a xor with '-1' for
checking a true value vector
for instance,
%cmp4.i = icmp ne <8 x i32> %6, %5
%7 = xor <8 x i1> %cmp4.i, <i1 true, i1 true, i1 true, i1 true, i1 true, i1
true, i1 true, i1 true>
[use of %7]
results in vector of '-1' in the DAG. This also seems the reason why
LLVM's vnot PatFrag
2009 Apr 30
6
[LLVMdev] RFC: AVX Pattern Specification [LONG]
...55, MRMSrcReg,
(outs VR128:$dst), (ins VR128:$src1, VR128:$src2),
"andnps\t{$src2, $dst|$dst, $src2}",
[(set VR128:$dst,
(v2i64 (and (xor VR128:$src1,
(bc_v2i64 (v4i32 immAllOnesV))),
VR128:$src2)))]>;
SSE2 :
def ANDNPDrr : PDI<0x55, MRMSrcReg,
(outs VR128:$dst), (ins VR128:$src1, VR128:$src2),
"andnpd\t{$src2, $dst|$dst, $src2}",
[(set VR128:$dst,...