Displaying 13 results from an estimated 13 matches for "noinf".
Did you mean:
ninf
2019 Mar 16
3
[RFC] Making space for a flush-to-zero flag in FastMathFlags
...could steal 4
bits.
3. Allow only specific combinations in FastMathFlags. In practice, I
don't think folks are equally interested in all the 2^N combinations
present in FastMathFlags, so we could compromise and allow only the
most "typical" 2^7 combinations (e.g. we could nonan and noinf into a
single bit, under the assumption that users want to enable-disable
them as a unit). I'm unsure if establishing the most typical 2^7
combinations will be straightforward though.
4. Function level attributes. Instead of wasting precious
instruction-level space, we could move all FP math...
2019 Mar 18
2
[RFC] Making space for a flush-to-zero flag in FastMathFlags
...low only specific combinations in FastMathFlags. In practice, I
>> don't think folks are equally interested in all the 2^N combinations
>> present in FastMathFlags, so we could compromise and allow only the
>> most "typical" 2^7 combinations (e.g. we could nonan and noinf into a
>> single bit, under the assumption that users want to enable-disable
>> them as a unit). I'm unsure if establishing the most typical 2^7
>> combinations will be straightforward though.
>>
>> 4. Function level attributes. Instead of wasting precious
>&g...
2019 Mar 18
3
[RFC] Making space for a flush-to-zero flag in FastMathFlags
...low only specific combinations in FastMathFlags. In practice, I
>> don't think folks are equally interested in all the 2^N combinations
>> present in FastMathFlags, so we could compromise and allow only the
>> most "typical" 2^7 combinations (e.g. we could nonan and noinf into a
>> single bit, under the assumption that users want to enable-disable
>> them as a unit). I'm unsure if establishing the most typical 2^7
>> combinations will be straightforward though.
>>
>> 4. Function level attributes. Instead of wasting precious
>&g...
2012 Nov 16
0
[LLVMdev] [llvm-commits] [PATCH] fast-math patches!
Michael,
Overall the code looks good.
80-cols:
2046 FMF.UnsafeAlgebra = 0 != (Record[OpNum] & (1 << bitc::FMF_UNSAFE_ALGEBRA));
2047 FMF.NoNaNs = 0 != (Record[OpNum] & (1 << bitc::FMF_NO_NANS));
2048 FMF.NoInfs = 0 != (Record[OpNum] & (1 << bitc::FMF_NO_INFS));
2049 FMF.NoSignedZeros = 0 != (Record[OpNum] & (1 << bitc::FMF_NO_SIGNED_ZEROS));
2050 FMF.AllowReciprocal = 0 != (Record[OpNum] & (1 << bitc::FMF_ALLOW_RECIPROCAL));
I found some more...
2012 Nov 16
2
[LLVMdev] [llvm-commits] [PATCH] fast-math patches!
...; wrote:
>
> On Nov 15, 2012, at 3:23 PM, Joe Abbey <joe.abbey at gmail.com> wrote:
>
>> Though semantically equivalent in this case, however I think you should use logical ors here not bitwise.
>>
>> + bool any() {
>> + return UnsafeAlgebra | NoNaNs | NoInfs | NoSignedZeros |
>> + AllowReciprocal;
>> + }
>>
>
> Will do.
>
>> Gripe: This pattern is probably super fast and has precedence… but the code is non-obvious:
>>
>> SubclassOptionalData =
>> (SubclassOptionalData & ~BitToSet) | (B...
2012 Nov 15
2
[LLVMdev] [llvm-commits] [PATCH] fast-math patches!
Though semantically equivalent in this case, however I think you should use logical ors here not bitwise.
+ bool any() {
+ return UnsafeAlgebra | NoNaNs | NoInfs | NoSignedZeros |
+ AllowReciprocal;
+ }
Gripe: This pattern is probably super fast and has precedence… but the code is non-obvious:
SubclassOptionalData =
(SubclassOptionalData & ~BitToSet) | (B * BitToSet);
This is likely one iota slower.. but it sure is easier to get the intent....
2012 Nov 15
0
[LLVMdev] [llvm-commits] [PATCH] fast-math patches!
On Nov 15, 2012, at 3:23 PM, Joe Abbey <joe.abbey at gmail.com> wrote:
> Though semantically equivalent in this case, however I think you should use logical ors here not bitwise.
>
> + bool any() {
> + return UnsafeAlgebra | NoNaNs | NoInfs | NoSignedZeros |
> + AllowReciprocal;
> + }
>
Will do.
> Gripe: This pattern is probably super fast and has precedence… but the code is non-obvious:
>
> SubclassOptionalData =
> (SubclassOptionalData & ~BitToSet) | (B * BitToSet);
>
This is an existing pa...
2016 Nov 18
2
what does -ffp-contract=fast allow?
...FMF (as well as storing all FMF in
> metadata) was discussed here:
> https://llvm.org/bugs/show_bug.cgi?id=13118
> 3. The backend needs a thread of its own. We have at least these
> mechanisms to handle FMA codegen:
> a. TargetOptions for LessPreciseFPMADOption, UnsafeFPMath,
> NoInfsFPMath, NoNaNsFPMath, AllowFPOpFusion (Fast, Standard, Strict)
> b. SDNodeFlags for UnsafeAlgebra, NoNaNs, NoInfs, NoSignedZeros (but
> nothing for FMA since IR FMF has nothing for FMA)
> c. SelectionDAGTargetInfo::generateFMAsInMachineCombiner()
> d. TargetLoweringBase::isFMAFasterT...
2016 Nov 18
2
what does -ffp-contract=fast allow?
Sent from my Verizon Wireless 4G LTE DROID
On Nov 17, 2016 5:53 PM, Mehdi Amini <mehdi.amini at apple.com<mailto:mehdi.amini at apple.com>> wrote:
>
>
>> On Nov 17, 2016, at 4:33 PM, Hal Finkel <hfinkel at anl.gov<mailto:hfinkel at anl.gov>> wrote:
>>
>>
>> ________________________________
>>>
>>> From: "Warren
2019 Oct 28
6
RFC: Matrix math support
...Store a matrix with M rows and N columns, using a stride of %Stride between columns. This allows for convenient storing of sub matrixes.
The floating point versions of the intrinsics also take fast-math flags, which can be used to opt-in to FMA generation and/or constant folding opportunities via NoInfs and NoNaNs. We plan to add them to the lowered instructions and rely on InstCombine & Co for related optimisations.
The intrinsics will be lowered to regular LLVM vector operations in a IR lowering pass. This means per default, we can lower the builtins on all targets. Additionally, targets c...
2012 Nov 15
0
[LLVMdev] [llvm-commits] [PATCH] fast-math patches!
Trying to apply patches..
What's your base revision?
Joe
On Nov 15, 2012, at 5:44 PM, Michael Ilseman <milseman at apple.com> wrote:
> New patches with review feedback incorporated:
> * Changed single letter flags to short abbreviations ('S' ==> 'nsz')
> * Indentation fixes
> * Comments don't state function names
>
>
2012 Nov 15
3
[LLVMdev] [PATCH] fast-math patches!
New patches with review feedback incorporated:
* Changed single letter flags to short abbreviations ('S' ==> 'nsz')
* Indentation fixes
* Comments don't state function names
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Fast-math-flags-added-to-FPMathOperator.patch
Type: application/octet-stream
Size: 4937 bytes
Desc: not
2017 Oct 04
2
Trouble when suppressing a portion of fast-math-transformations
> It might be clearer, instead of using 'libm', to use something like 'trans' (for transcendental functions).
That does seem clearer. ‘trans’ is definitely good with me.
-Warren
From: Hal Finkel [mailto:hfinkel at anl.gov]
Sent: Tuesday, October 3, 2017 5:13 PM
To: Ristow, Warren; Bruce Hoult
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Trouble when suppressing a