Displaying 20 results from an estimated 23 matches for "nearbyint".
2020 Mar 03
5
Should rint and nearbyint be always constrained?
>
> One concern with replacing llvm.rint and llvm.nearbyint with
> llvm.roundeven makes it difficult to turn back into a libcall if the
> backend doesn't have an instruction for it. You can't just call the
> roundeven library function since that wouldn't exist in older libm
> implementations. So ideally you would know which function...
2020 Mar 03
2
Should rint and nearbyint be always constrained?
>
> The only issue I see is that since we also assume FP operations have no
> side effects by default there is no difference between llvm.rint and
> llvm.nearbyint. I wouldn’t have a problem with dropping llvm.rint
> completely.
The forthcoming C standard (
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2454.pdf, 7.12.9.8)
defines new function, `roundeven`, which implements IEEE-754 operation
`roundToIntegralTiesToEven`. When corresponding intrinsic wi...
2020 Mar 02
2
Should rint and nearbyint be always constrained?
Some clarification after getting feedback from Craig Topper….
It’s probably best to say in the documentation that the llvm.nearbyint and llvm.rint functions “assume the default rounding mode, roundToNearest”. This will allow the optimizer to transform them as if they were rounding to nearest without requiring backends to use an encoding that enforces roundToNearest as the rounding mode for these operations. On modern x86 targets...
2020 Mar 02
2
Should rint and nearbyint be always constrained?
...default mode assumes that the current rounding mode is the
> default rounding mode. But the same holds true for many other
> intrinsics and even the arithmetic IR operations like add.
Any other intrinsic, like `floor`, `round` etc has meaning at default
rounding mode. But use of `rint` or `nearbyint` in default FP environment
is strange, `roundeven` can be used instead. We could use more general
intrinsics in all cases, as the special case of default environment is not
of practical interest.
There is another reason for special handling. Set of intrinsics includes
things like `x86_sse_cvtss2si...
2020 Mar 02
2
Should rint and nearbyint be always constrained?
...fo about current FP
environment and have attribute `IntrInaccessibleMemOnly` that helps keeping
order of operations that access FP environment. Non-constrained intrinsics
are considered as working solely in default FP environment.
This approach has issues when applied to the intrinsics `rint` and
`nearbyint`. Value returned by either of these intrinsics depends on
current rounding mode. If they are considered as operation in default
environment, they would round only to nearest. It is by far not the meaning
of the standard C functions that these intrinsics represent.
So the unconstrained intrinsics `...
2013 Jun 19
1
[LLVMdev] round() vs. rint()/nearbyint() with fast-math
Hello,
Sometime over the last few months, I implemented in the PowerPC backend a fast-math-only optimization which lowers ISD::FRINT/FNEARBYINT in terms of the frin instruction (when supported). As one of my users has pointed out to me, frin actually implements the semantics of round() [it ties away from zero] instead of implementing nearbyint() [which ties to even]. This user has additionally pointed out that LLVM on x86 does not lower ro...
2020 Mar 05
3
Should rint and nearbyint be always constrained?
...at the user has promised that at this point during execution,
> we will *always* have the default FP environment.
>
This is a strong statement (no pragma == default mode), we need to confirm
it with proper references to the standard. If it is true and the code:
float qqq(float x) {
return nearbyint(x);
}
is really equivalent to:
float qqq(float x) {
return roundeven(x);
}
(in absence of 'pragma STD FENV_ACCESS), it is a fact that would be
surprise for many user.
Thanks,
--Serge
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.o...
2013 Jul 05
1
[LLVMdev] round() vs. rint()/nearbyint() with fast-math
...t arm.com >
> wrote:
>
>
>
>
>
>
> | LLVM does not currently have special lowering handling for round(),
> | and
> I'll propose a patch to add that, but the larger question is this:
> should
> fast-math change the tie-breaking behavior of
> | rint/nearbyint/round, etc. and, if so, should we make a specific
> | effort to
> have all backends provide the same guarantee (or lack of a guarantee)
> in
> this regard?
>
> I don't know, primarily because I've never really been involved in
> anything
> where I've cared about...
2013 Jun 21
2
[LLVMdev] round() vs. rint()/nearbyint() with fast-math
...un 21, 2013 at 7:54 AM, David Tweed <david.tweed at arm.com> wrote:
> | LLVM does not currently have special lowering handling for round(), and
> I'll propose a patch to add that, but the larger question is this: should
> fast-math change the tie-breaking behavior of
> | rint/nearbyint/round, etc. and, if so, should we make a specific effort
> to
> have all backends provide the same guarantee (or lack of a guarantee) in
> this regard?
>
> I don't know, primarily because I've never really been involved in anything
> where I've cared about using exotic...
2013 Jul 04
0
[LLVMdev] round() vs. rint()/nearbyint() with fast-math
...AM, David Tweed <david.tweed at arm.com> wrote:
>
>> | LLVM does not currently have special lowering handling for round(), and
>> I'll propose a patch to add that, but the larger question is this: should
>> fast-math change the tie-breaking behavior of
>> | rint/nearbyint/round, etc. and, if so, should we make a specific effort
>> to
>> have all backends provide the same guarantee (or lack of a guarantee) in
>> this regard?
>>
>> I don't know, primarily because I've never really been involved in
>> anything
>> where...
2016 Nov 25
0
Wine release 1.9.24
...1602 Videos do not play in Age of Empires
41640 add rx 480 into directx.c
41671 GOG Galaxy requires unimplemented function vcruntime140.dll.__std_terminate
41683 Gauntlet start background is corrupted.
41695 LeagueClient.exe Call to unimplemented function api-ms-win-crt-math-l1-1-0.dll.nearbyint
41705 Build fails in dpnet: redefinition of typedef 'SOCKADDR'
41719 crypt32:store test regression in testRegStoreSavedCerts()
41721 hidtest.exe crashes on unimplemented function hid.dll.HidP_GetSpecificButtonCaps
41736 build error: configure detects udev only partly
----------...
2008 Sep 21
2
[LLVMdev] OpenBSD port in progress
...re more involved.
The first one is Feature/load_module.ll. It fails because the library
is called LLVMHello.so.0.0 rather than LLVMHello.so. I have a local
patch that renames the lib in the test that I doubt should be applied
to the tree.
The second one is Transforms/SimplifyLibCalls/floor.ll. nearbyint is
not replaced by nearbyintf since neither function is defined in the
OpenBSD libm. The other two are replaced fine though. My crude
solution was to remove checking for nearbyintf.
The third one is Assembler/2004-02-01-NegativeZero.ll. This fails
because the constants are printed as positive z...
2018 Feb 06
2
libc++ cross-compile linux-armv7 and math function problems
...g int lround(long
double)':
../projects/libcxx/include/math.h:1334:86: error: '::lroundl' has not been
declared
inline _LIBCPP_INLINE_VISIBILITY long lround(long double __lcpp_x)
_NOEXCEPT {return ::lroundl(__lcpp_x);}
^~
../projects/libcxx/include/math.h: In function 'long double nearbyint(long
double)':
../projects/libcxx/include/math.h:1346:96: error: '::nearbyintl' has not
been declared
inline _LIBCPP_INLINE_VISIBILITY long double nearbyint(long double
__lcpp_x) _NOEXCEPT {return ::nearbyintl(__lcpp_x);}
^~
../projects/libcxx/inclu...
2018 Feb 06
0
libc++ cross-compile linux-armv7 and math function problems
...; has not been declared
> inline _LIBCPP_INLINE_VISIBILITY long lround(long double __lcpp_x) _NOEXCEPT {return ::lroundl(__lcpp_x);}
> ^~
> ../projects/libcxx/include/math.h: In function 'long double nearbyint(long double)':
> ../projects/libcxx/include/math.h:1346:96: error: '::nearbyintl' has not been declared
> inline _LIBCPP_INLINE_VISIBILITY long double nearbyint(long double __lcpp_x) _NOEXCEPT {return ::nearbyintl(__lcpp_x);}
>...
2018 Feb 06
1
libc++ cross-compile linux-armv7 and math function problems
...h.h:1334:86: error: '::lroundl' has not
> been declared
> > inline _LIBCPP_INLINE_VISIBILITY long lround(long double __lcpp_x)
> _NOEXCEPT {return ::lroundl(__lcpp_x);}
> >
> ^~
> > ../projects/libcxx/include/math.h: In function 'long double
> nearbyint(long double)':
> > ../projects/libcxx/include/math.h:1346:96: error: '::nearbyintl' has
> not been declared
> > inline _LIBCPP_INLINE_VISIBILITY long double nearbyint(long double
> __lcpp_x) _NOEXCEPT {return ::nearbyintl(__lcpp_x);}
> >
>...
2018 Feb 05
0
Cross-compiling libc++ to linux-armv7hf gives undefined symbols in cmath / math.h
...g int lround(long
double)':
../projects/libcxx/include/math.h:1334:86: error: '::lroundl' has not been
declared
inline _LIBCPP_INLINE_VISIBILITY long lround(long double __lcpp_x)
_NOEXCEPT {return ::lroundl(__lcpp_x);}
^~
../projects/libcxx/include/math.h: In function 'long double nearbyint(long
double)':
../projects/libcxx/include/math.h:1346:96: error: '::nearbyintl' has not
been declared
inline _LIBCPP_INLINE_VISIBILITY long double nearbyint(long double
__lcpp_x) _NOEXCEPT {return ::nearbyintl(__lcpp_x);}
^~
../projects/libcxx/include/math.h: In function 'long dou...
2012 Aug 02
2
[LLVMdev] Proposal to merge SimplifyLibCalls into InstCombiner
...r,
memcmp, memcpy, memmove, memset, __strcpy_chk, cosf, cos, cosl, powf,
pow, powl, llvm.pow.f32, llvm.pow.f64, llvm.pow.f80, llvm.pow.f128,
llvm.pow.ppcf128, exp21, exp2, exp2f, llvm.exp2.ppcf128, llvm.exp2.f128,
llvm.exp2.f80, llvm.exp2.f64, llvm.exp2.f32, floor, cell, round, rint,
nearbyint, ffs, ffsl, ffsll, abs, labs, llabs, isdigit, isascii,
toascii, sprintf, print, fwrite, fputs, fprintf, puts.
Test cases that exercise the library call folders for each of these
functions should be present. Any missing test cases will be added.
Create new `LibCallSimplifier` class
-----------...
2015 Jan 20
3
[LLVMdev] strlen in fast-isel
It seems that fast-isel for intel does not handle strlen. It's a general
problem in fast-isel .
~/llvmw/build/Deb~/llvmw/build/Debug+Asserts/bin/clang -O0 -mllvm
-fast-isel-verbose -mllvm -fast-isel strlen1.c
strlen1.c:12:3: warning: implicitly declaring library function 'printf' with
type 'int (const char *, ...)'
printf("%i\n", len);
^
2012 Dec 03
0
need help for R's installation
...lared... yes
checking whether expm1 exists and is declared... yes
checking whether hypot exists and is declared... yes
checking whether log1p exists and is declared... yes
checking whether log2 exists and is declared... yes
checking whether log10 exists and is declared... yes
checking whether nearbyint exists and is declared... yes
checking whether nearbyintl exists and is declared... yes
checking whether powl exists and is declared... yes
checking whether rint exists and is declared... yes
checking whether rintl exists and is declared... yes
checking whether va_copy exists and is declared.....
2016 Jan 04
2
R, AIX 64-bit builds - trying to understand root cause for message: "Error: Line starting 'Package: tools ...' is malformed!"
The bulk is on my forums - the final post for today is:
Results to date:
A. It looks like I am going to need a newer compiler for C - xlc/xlC V11
apparently does not understand this code:
"/data/prj/cran/R-3.2.3/src/main/memory.c", line 2149.31: 1506-046 (S)
Syntax error.
I will have to check if R-devel has different code before asking for
assistence.
+2139 #ifdef