Displaying 7 results from an estimated 7 matches for "v32f32".
Did you mean:
v2f32
2017 Jul 11
2
error: In anonymous_4820: Unrecognized node 'VRR128'!
hello,
i need to use v32i32 and v32f32 in store instructions.
I defined my register as;
def VRR128 : RegisterClass<"X86", [v32i32, v32f32],
1024, (add R_0_V_0, R_1_V_0, R_2_V_0)>;
def STORE_DWORD : I<0x70, MRMDestMem, (outs), (ins i2048mem:$dst,
VRR128:$src),
"STORE...
2017 Jul 11
2
error: In anonymous_4820: Unrecognized node 'VRR128'!
...x0E, MRMDestReg, (outs VRR128:$dst), (ins VRR128:$src1,
VRR128:$src2),"VADD\t{$src1, $src2, $dst|$dst, $src1, $src2}", [(set
VRR128:$dst, (add VRR128:$src1, VRR128:$src2))]>, TA;
def : Pat<(add VRR128:$src1, VRR128:$src2), (VADD VRPIM128:$src1,
VRPIM128:$src2)>;
Where to place v32f32 to distinguish between the two?
On Tue, Jul 11, 2017 at 7:55 PM, Craig Topper <craig.topper at gmail.com>
wrote:
> You need a type inside this bitconvert. The outer type is the destination
> type for the bitconvert but it also needs an input type
>
> (store (v32i32 (bitconvert V...
2017 Jul 11
2
Using new types v32f32, v32f64 in llvm backend not possible
Hello,
i want to work with these types v32f32, v32f64.... in llvm which are
undefined in the backend?
But v32i32, v32i64 are already defined so i am able to use these.
but for other types such as v32f32, v32f64 although i have defined them
appropriately in all the files like machinevaluetype.h, valuetypes.cpp
etc. i have checked it many time...
2017 Jul 11
2
error: In anonymous_4820: Unrecognized node 'VRR128'!
...1,
>> VRR128:$src2),"VADD\t{$src1, $src2, $dst|$dst, $src1, $src2}", [(set
>> VRR128:$dst, (add VRR128:$src1, VRR128:$src2))]>, TA;
>>
>> def : Pat<(add VRR128:$src1, VRR128:$src2), (VADD VRPIM128:$src1,
>> VRPIM128:$src2)>;
>> Where to place v32f32 to distinguish between the two?
>>
>> On Tue, Jul 11, 2017 at 7:55 PM, Craig Topper <craig.topper at gmail.com>
>> wrote:
>>
>>> You need a type inside this bitconvert. The outer type is the
>>> destination type for the bitconvert but it also needs an...
2017 Jul 11
2
Using new types v32f32, v32f64 in llvm backend not possible
....
How to accomplish this???
I am really stuck at this point.
Please guide me.
Thank You
On Tue, Jul 11, 2017 at 6:20 PM, Hal Finkel <hfinkel at anl.gov> wrote:
>
> On 07/11/2017 03:22 AM, hameeza ahmed wrote:
>
>> Hello,
>>
>> i want to work with these types v32f32, v32f64.... in llvm which are
>> undefined in the backend?
>> But v32i32, v32i64 are already defined so i am able to use these.
>>
>> but for other types such as v32f32, v32f64 although i have defined them
>> appropriately in all the files like machinevaluetype.h, val...
2017 Jul 12
2
Using new types v32f32, v32f64 in llvm backend not possible
...; Thank You
>>
>>
>> On Tue, Jul 11, 2017 at 6:20 PM, Hal Finkel <hfinkel at anl.gov> wrote:
>>
>>>
>>> On 07/11/2017 03:22 AM, hameeza ahmed wrote:
>>>
>>>> Hello,
>>>>
>>>> i want to work with these types v32f32, v32f64.... in llvm which are
>>>> undefined in the backend?
>>>> But v32i32, v32i64 are already defined so i am able to use these.
>>>>
>>>> but for other types such as v32f32, v32f64 although i have defined them
>>>> appropriately in all...
2020 Jun 30
5
[RFC] Semi-Automatic clang-format of files with low frequency
I 100% get that we might not like the decisions clang-format is making, but
how does one overcome this when adding new code? The pre-merge checks
enforce clang-formatting before commit and that's a common review comment
anyway for those who didn't join the pre-merge checking group. I'm just
wondering are we not all following the same guidelines?
Concerns of clang-format not being good