Displaying 7 results from an estimated 7 matches for "_eq_f32".
2009 Sep 29
2
[LLVMdev] SoftenSetCCOpernads in LegalizeFloatTypes.cpp
...of the softening code assumes you are dealing
> with float (32 bits). So it's not just a matter of changing the libcall
> return type.
>
Yes, we are dealing with 32-bits only. But why the cmp libcalls have to
return a 32-bit value.
e.g. Our libcall for comparing two floats is
char _eq_f32 (float a, float b);
rather than
long _eq_f32 (float a, float b);
- Sanjiv
2009 Oct 05
2
[LLVMdev] SoftenSetCCOpernads in LegalizeFloatTypes.cpp
...atter of changing the libcall
>>> return type.
>>>
>>>
>>>
>> Yes, we are dealing with 32-bits only. But why the cmp libcalls have to
>> return a 32-bit value.
>> e.g. Our libcall for comparing two floats is
>>
>> char _eq_f32 (float a, float b);
>>
>> rather than
>>
>> long _eq_f32 (float a, float b);
>>
>>
>> - Sanjiv
>>
>>
> Why not use TLI.getSetCCResultType () ?
>
> - Sanjiv
>
>
Duncan,
Any thoughts ?
Or am I missing something very o...
2009 Sep 30
0
[LLVMdev] SoftenSetCCOpernads in LegalizeFloatTypes.cpp
...> with float (32 bits). So it's not just a matter of changing the libcall
>> return type.
>>
>>
> Yes, we are dealing with 32-bits only. But why the cmp libcalls have to
> return a 32-bit value.
> e.g. Our libcall for comparing two floats is
>
> char _eq_f32 (float a, float b);
>
> rather than
>
> long _eq_f32 (float a, float b);
>
>
> - Sanjiv
>
Why not use TLI.getSetCCResultType () ?
- Sanjiv
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http...
2009 Oct 05
0
[LLVMdev] SoftenSetCCOpernads in LegalizeFloatTypes.cpp
...ibcall
>>>> return type.
>>>>
>>>>
>>>>
>>> Yes, we are dealing with 32-bits only. But why the cmp libcalls have to
>>> return a 32-bit value.
>>> e.g. Our libcall for comparing two floats is
>>>
>>> char _eq_f32 (float a, float b);
>>>
>>> rather than
>>>
>>> long _eq_f32 (float a, float b);
>>>
>>>
>>> - Sanjiv
>>>
>>>
>> Why not use TLI.getSetCCResultType () ?
>>
>> - Sanjiv
>>
>>
> Duncan,...
2009 Dec 25
1
[LLVMdev] SoftenSetCCOpernads in LegalizeFloatTypes.cpp
...t;>
> >>>>
> >>>>
> >>> Yes, we are dealing with 32-bits only. But why the cmp libcalls
> have to
> >>> return a 32-bit value.
> >>> e.g. Our libcall for comparing two floats is
> >>>
> >>> char _eq_f32 (float a, float b);
> >>>
> >>> rather than
> >>>
> >>> long _eq_f32 (float a, float b);
> >>>
> >>>
> >>> - Sanjiv
> >>>
> >>>
> >> Why not use TLI.getSetCCResultType ()...
2009 Sep 29
2
[LLVMdev] SoftenSetCCOpernads in LegalizeFloatTypes.cpp
While generating a libcall from floating point comparison, it always
assumes that the return type of those libcalls is i32.
Why not allow Targets to provide the correct return type?
EVT RetVT = MVT::i32; // <-- here
SDValue Ops[2] = { LHSInt, RHSInt };
NewLHS = MakeLibCall(LC1, RetVT, Ops, 2, false/*sign irrelevant*/, dl);
NewRHS = DAG.getConstant(0, RetVT);
CCCode =
2009 Sep 29
0
[LLVMdev] SoftenSetCCOpernads in LegalizeFloatTypes.cpp
Hi Sanjiv, I think a lot of the softening code assumes you are dealing
with float (32 bits). So it's not just a matter of changing the libcall
return type.
> While generating a libcall from floating point comparison, it always
> assumes that the return type of those libcalls is i32.
> Why not allow Targets to provide the correct return type?
>
> EVT RetVT = MVT::i32;