Displaying 4 results from an estimated 4 matches for "relaxed_float".
2010 Mar 03
3
[LLVMdev] folding x * 0 = 0
> I'm not sure how that would work, but it most likely wouldn't fit with the design of llvm. If this is important, I'd rather fix the representational issue.
>
>
Just
#ifdef RELAXED_FLOAT
here the code like I posted
#endif
what do you mean by the representational issue? something in the IR?
Perhaps something like the value tracking can be implemented that
tracks if a float can be NaN. then only a flag is needed for the load
instruction that the float from memory is assumed not to b...
2010 Mar 03
0
[LLVMdev] folding x * 0 = 0
On Mar 3, 2010, at 11:07 AM, Jochen Wilhelmy wrote:
>
>> These flags only affect the code generator. If you want to add this optimization to your copy of llvm, you can do so by adding it to the instcombine pass. We'd need IR enhancements to do this sort of thing for real in the mid-level optimizer, some thoughts are here:
>>
2010 Mar 03
0
[LLVMdev] folding x * 0 = 0
On Mar 3, 2010, at 12:41 PM, Jochen Wilhelmy wrote:
>
>> I'm not sure how that would work, but it most likely wouldn't fit with the design of llvm. If this is important, I'd rather fix the representational issue.
>>
>>
> Just
> #ifdef RELAXED_FLOAT
> here the code like I posted
> #endif
Ok, that's what I thought, we don't want that in mainline.
> what do you mean by the representational issue? something in the IR?
Yes. Each fp operation should have the information tagged onto like (like nuw/nsw on integer ops). This allo...
2010 Mar 03
3
[LLVMdev] folding x * 0 = 0
> These flags only affect the code generator. If you want to add this optimization to your copy of llvm, you can do so by adding it to the instcombine pass. We'd need IR enhancements to do this sort of thing for real in the mid-level optimizer, some thoughts are here:
> http://nondot.org/sabre/LLVMNotes/FloatingPointChanges.txt
>
Thanks, now it works. I inserted
if