Displaying 7 results from an estimated 7 matches for "gmp5".
Did you mean:
gmp
2012 Oct 23
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
Hi Jack,
> It is interesting though that LLVMPolly.so shows the linkage...
>
> /sw/opt/llvm-3.2/lib/LLVMPolly.so:
> /sw/lib/libisl.10.dylib (compatibility version 11.0.0, current version 11.0.0)
> /sw/lib/gmp5/libgmp.10.dylib (compatibility version 11.0.0, current version 11.5.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
...
> However I have managed to shift the error wi...
2012 Oct 23
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
...b (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.3.0)
It is interesting though that LLVMPolly.so shows the linkage...
/sw...
2012 Oct 23
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
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
2012 Oct 22
5
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
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
2012 Oct 22
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
.../cc1
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007fff5fc0109d in __dyld_dyld_fatal_error ()
The linkage is...
% otool -L /sw/opt/llvm-3.2/lib/LLVMPolly.so
/sw/opt/llvm-3.2/lib/LLVMPolly.so:
/sw/lib/libisl.10.dylib (compatibility version 11.0.0, current version 11.0.0)
/sw/lib/gmp5/libgmp.10.dylib (compatibility version 11.0.0, current version 11.5.0)
/sw/lib/libcloog-isl.3.dylib (compatibility version 4.0.0, current version 4.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, curr...
2013 Nov 19
2
[LLVMdev] proposed patch to default to isl-only polly
...apple-darwin12 with cloog 0.18.1 and isl 0.12.1
installed and it works fine. The default build of Polly is isl-only as expected.
% otool -L /sw/opt/llvm-3.4/lib/LLVMPolly.so
/sw/opt/llvm-3.4/lib/LLVMPolly.so:
/sw/lib/libisl.10.dylib (compatibility version 13.0.0, current version 13.1.0)
/sw/lib/gmp5/libgmp.10.dylib (compatibility version 12.0.0, current version 12.3.0)
/sw/lib/ncurses/libncurses.5.dylib (compatibility version 5.0.0, current version 5.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, cur...
2012 Oct 22
5
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
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