search for: __acoshf128_finite

...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_finite at GLIBC_2.15 ) but maybe it needs some help on that regard ? Thanks for your quick answer, Jean-Michaël On Mon, Oct 5, 2020 at 7:53 PM Lang Hames <lhames at gmail.com> wrote: > Hi Jean-Michaël, > > How are you trying to provide...

...ese __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_finite at GLIBC_2.15 >> ) >> but maybe it needs some help on that regard ? >> >> Thanks for your quick answer, >> >> Jean-Michaël >> >> >> On Mon, Oct 5, 2020 at 7:53 PM Lang Hames <lhames...

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 -