Displaying 3 results from an estimated 3 matches for "__finite".
Did you mean:
r_finite
2020 Oct 05
2
LLJIT: __{math}_finite symbols not resolved ?
Hello,
Right now I am just using a Generator to look for symbols in my process
(which links dynamically against libc / libm).
It seems to have no trouble finding every other libc / libm / libc++ / ...
symbol so I assumed that it was not necessary to specifically link against
libm where these __finite symbols reside:
$ nm -D /usr/lib/libm.so.6 | grep finite
0000000000050540 T __acosf128_finite at GLIBC_2.26
0000000000042f70 T __acosf_finite at GLIBC_2.15
0000000000026940 i __acos_finite at GLIBC_2.15
0000000000051000 T __acoshf128_finite at GLIBC_2.26
0000000000043240 T __acoshf_fi...
2020 Oct 05
2
LLJIT: __{math}_finite symbols not resolved ?
...ing a Generator to look for symbols in my process
>> (which links dynamically against libc / libm).
>> It seems to have no trouble finding every other libc / libm / libc++ /
>> ... symbol so I assumed that it was not necessary to specifically link
>> against libm where these __finite symbols reside:
>>
>> $ nm -D /usr/lib/libm.so.6 | grep finite
>> 0000000000050540 T __acosf128_finite at GLIBC_2.26
>> 0000000000042f70 T __acosf_finite at GLIBC_2.15
>> 0000000000026940 i __acos_finite at GLIBC_2.15
>> 0000000000051000 T __acoshf128_...
2020 Oct 05
2
LLJIT: __{math}_finite symbols not resolved ?
Hello,
when building code with -Ofast -ffinite-math-only -ffast-math, clang
generates calls to "finite" variants of math functions.
This has been the source of a fair amount of issues in a "normal", non-JIT
pipeline, which seem to have been fixed over time - a simple fix being
recompiling the target app against the new glibc.
- https://bugs.llvm.org/show_bug.cgi?id=44842
-