search for: libmpfr

...rely on the host math library. Because long double isn't portable, we only ever query the host math library for double or float results. I can see three methods for allowing constant folding for types that are larger than double, some more expensive than others: 1. Introduce a dependency on libMPFR, as GCC does. The dependency could be hard or soft, with a fallback to the current behaviour if it doesn't exist. 2. Write the trancendental functions ourselves in APFloat (yuck!) 3. If the long double format on the compiler host is the same as the target, use the host library. (2) is the...

...are used with -ffast-math, and the more-accurate ones otherwise. For non-finite inputs and outputs, the library should return the same results as libm. The library is tested if the evaluation error is within the designed limit. The library is tested against high-precision evaluation using the libmpfr library. Especially, we rigorously checked the error of the trigonometric functions when the arguments are close to an integral multiple of PI/2. The size of the functions is very small. Implementation of the library: Basically, each function consists of reduction and kernel. For the kernel,...

...cause long double isn't > portable, we only ever query the host math library for double or float > results. > > I can see three methods for allowing constant folding for types that are > larger than double, some more expensive than others: > > 1. Introduce a dependency on libMPFR, as GCC does. The dependency could > be hard or soft, with a fallback to the current behaviour if it doesn't > exist. > 2. Write the trancendental functions ourselves in APFloat (yuck!) > 3. If the long double format on the compiler host is the same as the > target, use the h...

...uld indeed add another dimension to the testing matrix. Do you have an alternative solution or a preferred solution of those I enumerated earlier? Cheers, James On Mon, 4 Apr 2016 at 15:24 Neil Henning <llvm at duskborn.com> wrote: > Hey James, > > I really fundamentally dislike libMPFR. > > License of the codebase aside, would a dependency be on the built .so, or > would it be that we'd want to pull in the code and build that? > > My worry if we do bring it in even as a soft dependency is how is this > figured out - is it a case that CMake will, if it finds...

...ill be installed --> Processing Dependency: libppl_c.so.2()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64 --> Processing Dependency: libppl.so.7()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64 ---> Package cpp.x86_64 0:4.4.7-3.el6 will be installed --> Processing Dependency: libmpfr.so.1()(64bit) for package: cpp-4.4.7-3.el6.x86_64 ---> Package glibc-devel.x86_64 0:2.12-1.107.el6_4.4 will be installed --> Processing Dependency: glibc-headers = 2.12-1.107.el6_4.4 for package: glibc-devel-2.12-1.107.el6_4.4.x86_64 --> Processing Dependency: glibc-headers for package: gl...

...>> portable, we only ever query the host math library for double or float >> results. >> >> I can see three methods for allowing constant folding for types that are >> larger than double, some more expensive than others: >> >> 1. Introduce a dependency on libMPFR, as GCC does. The dependency could >> be hard or soft, with a fallback to the current behaviour if it doesn't >> exist. >> 2. Write the trancendental functions ourselves in APFloat (yuck!) >> 3. If the long double format on the compiler host is the same as the >&g...

...ill be installed --> Processing Dependency: libppl_c.so.2()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64 --> Processing Dependency: libppl.so.7()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64 ---> Package cpp.x86_64 0:4.4.6-4.el6 will be installed --> Processing Dependency: libmpfr.so.1()(64bit) for package: cpp-4.4.6-4.el6.x86_64 ---> Package glibc-devel.x86_64 0:2.12-1.80.el6_3.7 will be installed --> Processing Dependency: glibc-headers = 2.12-1.80.el6_3.7 for package: glibc-devel-2.12-1.80.el6_3.7.x86_64 --> Processing Dependency: glibc-headers for package: glibc...

...ly ever query the host math library for double or float >>> results. >>> >>> I can see three methods for allowing constant folding for types that are >>> larger than double, some more expensive than others: >>> >>> 1. Introduce a dependency on libMPFR, as GCC does. The dependency >>> could be hard or soft, with a fallback to the current behaviour if it >>> doesn't exist. >>> 2. Write the trancendental functions ourselves in APFloat (yuck!) >>> 3. If the long double format on the compiler host is the sa...

...itm.spec go libltdl.so.7 i386 libltdl.so.7.3.0 lib-gnu-awt-xlib.so liblzma.so.5 lib-gnu-awt-xlib.so.15 liblzma.so.5.0.5 lib-gnu-awt-xlib.so.15.0.0 libmpc.so.3 libatomic.a libmpc.so.3.0.0 libatomic.la libmpfr.so.4 libatomic.so libmpfr.so.4.1.2 libatomic.so.1 libncurses.so.5 libatomic.so.1.1.0 libncurses.so.5.9 libaugeas.so libnetsnmp.so libaugeas.so.0 libnetsnmp.so.25 libaugeas.so.0.15.0 libnetsnmp.so.25.0.2 libcharset.so.1...

I'm having issues with getting Wine64 to even install properly. I'm using an AMD 64 processor with Fedora 14 x64. When I try to get things working, here's what I get with the gcc: Touching configure... [root at Iceburgh gcc-svn]# cd .. [root at Iceburgh Iceburgh]# rm -rf gcc-build [root at Iceburgh Iceburgh]# mkdir gcc-build [root at Iceburgh Iceburgh]# cd gcc-build [root at Iceburgh

...ompatibility version 10.0.0, current version 10.0.0) /sw/lib/libpwl.5.dylib (compatibility version 6.0.0, current version 6.0.0) /sw/lib/gmp5/libgmpxx.4.dylib (compatibility version 7.0.0, current version 7.5.0) /sw/lib/libmpc.3.dylib (compatibility version 4.0.0, current version 4.0.0) /sw/lib/libmpfr.4.dylib (compatibility version 6.0.0, current version 6.1.0) /sw/lib/gmp5/libgmp.10.dylib (compatibility version 11.0.0, current version 11.5.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169...

On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote: > Nick, > I have uploaded the full walk with 'set env DYLD_PRINT_INITIALIZERS'. It didn't seem very informative > as the dyld error occurs right after... > > (gdb) > llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8 "/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at

...cc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1: /sw/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.1.0) /sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /sw/lib/libmpc.3.dylib (compatibility version 4.0.0, current version 4.0.0) /sw/lib/libmpfr.4.dylib (compatibility version 6.0.0, current version 6.1.0) /sw/lib/gmp5/libgmp.10.dylib (compatibility version 11.0.0, current version 11.5.0) /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169...

Hi, > I looks like the code is calling dlopen() on LLVMPolly.so and it or something it links against has an initializer. The initialer is run before dlopen() returns and the crash is in the initializer. The message: > > dyld: fast lazy bind offset out of range (53437, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 > > means the initializer

Jack, I looks like the code is calling dlopen() on LLVMPolly.so and it or something it links against has an initializer. The initialer is run before dlopen() returns and the crash is in the initializer. The message: dyld: fast lazy bind offset out of range (53437, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 means the initializer called something which