Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] dragonegg polly support broken?"
2012 Oct 21
0
[LLVMdev] dragonegg polly support broken?
On 10/20/2012 05:38 PM, Jack Howarth wrote:
> Duncan,
> Is the documentation for using Polly support in dragonegg correct? I built llvm/polly/dragonegg
> using the documentation at http://polly.llvm.org/example_load_Polly_into_dragonegg.html
> with...
>
> GCC=/sw/lib/gcc4.7/bin/gcc-4 LLVM_CONFIG=/sw/opt/llvm-3.2/bin/llvm-config ENABLE_LLVM_PLUGINS=1 make
2012 Oct 21
2
[LLVMdev] dragonegg polly support broken?
On Sun, Oct 21, 2012 at 08:38:21AM -0700, Tobias Grosser wrote:
> On 10/20/2012 05:38 PM, Jack Howarth wrote:
>> Duncan,
>> Is the documentation for using Polly support in dragonegg correct? I built llvm/polly/dragonegg
>> using the documentation at http://polly.llvm.org/example_load_Polly_into_dragonegg.html
>> with...
>>
>> GCC=/sw/lib/gcc4.7/bin/gcc-4
2012 Oct 21
2
[LLVMdev] dragonegg polly support broken?
On Sun, Oct 21, 2012 at 10:38:48AM -0700, Tobias Grosser wrote:
> On 10/21/2012 09:13 AM, Jack Howarth wrote:
>> On Sun, Oct 21, 2012 at 08:38:21AM -0700, Tobias Grosser wrote:
>>> On 10/20/2012 05:38 PM, Jack Howarth wrote:
>>>> Duncan,
>>>> Is the documentation for using Polly support in dragonegg correct? I built llvm/polly/dragonegg
2012 Oct 21
2
[LLVMdev] dragonegg polly support broken?
On Sun, Oct 21, 2012 at 11:01:37AM -0700, Tobias Grosser wrote:
> On 10/21/2012 10:57 AM, Jack Howarth wrote:
>> On Sun, Oct 21, 2012 at 10:38:48AM -0700, Tobias Grosser wrote:
>>> On 10/21/2012 09:13 AM, Jack Howarth wrote:
>>>> On Sun, Oct 21, 2012 at 08:38:21AM -0700, Tobias Grosser wrote:
>>>>> On 10/20/2012 05:38 PM, Jack Howarth wrote:
2012 Oct 21
0
[LLVMdev] dragonegg polly support broken?
On 10/21/2012 09:13 AM, Jack Howarth wrote:
> On Sun, Oct 21, 2012 at 08:38:21AM -0700, Tobias Grosser wrote:
>> On 10/20/2012 05:38 PM, Jack Howarth wrote:
>>> Duncan,
>>> Is the documentation for using Polly support in dragonegg correct? I built llvm/polly/dragonegg
>>> using the documentation at
2012 Oct 21
0
[LLVMdev] dragonegg polly support broken?
On 10/21/2012 10:57 AM, Jack Howarth wrote:
> On Sun, Oct 21, 2012 at 10:38:48AM -0700, Tobias Grosser wrote:
>> On 10/21/2012 09:13 AM, Jack Howarth wrote:
>>> On Sun, Oct 21, 2012 at 08:38:21AM -0700, Tobias Grosser wrote:
>>>> On 10/20/2012 05:38 PM, Jack Howarth wrote:
>>>>> Duncan,
>>>>> Is the documentation for using Polly
2012 Oct 21
0
[LLVMdev] dragonegg polly support broken?
On Sun, Oct 21, 2012 at 02:35:49PM -0400, Jack Howarth wrote:
> On Sun, Oct 21, 2012 at 11:01:37AM -0700, Tobias Grosser wrote:
> > On 10/21/2012 10:57 AM, Jack Howarth wrote:
> >> On Sun, Oct 21, 2012 at 10:38:48AM -0700, Tobias Grosser wrote:
> >>> On 10/21/2012 09:13 AM, Jack Howarth wrote:
> >>>> On Sun, Oct 21, 2012 at 08:38:21AM -0700, Tobias
2012 Oct 24
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Oct 23, 2012, at 4:46 PM, Jack Howarth wrote:
> On Tue, Oct 23, 2012 at 02:03:15PM -0700, Nick Kledzik wrote:
>>
>> On Oct 23, 2012, at 1:57 PM, Jack Howarth wrote:
>>> Nick,
>>> Can I do this without access to a debug version of dyld? Using the copy of LLVMPolly.so with isl/cloog-isl/gmp statically linked,
>>> I find that if I set the breakpoint to
2012 Oct 23
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Tue, Oct 23, 2012 at 02:03:15PM -0700, Nick Kledzik wrote:
>
> On Oct 23, 2012, at 1:57 PM, Jack Howarth wrote:
> > Nick,
> > Can I do this without access to a debug version of dyld? Using the copy of LLVMPolly.so with isl/cloog-isl/gmp statically linked,
> > I find that if I set the breakpoint to the address of the initializer...
> >
> > dyld: calling
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 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 21
2
[LLVMdev] dragonegg polly support broken?
On 10/21/2012 11:46 AM, Jack Howarth wrote:
> On Sun, Oct 21, 2012 at 02:35:49PM -0400, Jack Howarth wrote:
>> On Sun, Oct 21, 2012 at 11:01:37AM -0700, Tobias Grosser wrote:
>>> On 10/21/2012 10:57 AM, Jack Howarth wrote:
>>>> On Sun, Oct 21, 2012 at 10:38:48AM -0700, Tobias Grosser wrote:
>>>>> On 10/21/2012 09:13 AM, Jack Howarth wrote:
2012 Oct 21
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
Nick,
While enhancing the fink llvm32 packaging to support the polly tool, I ran into
a dyld failure when the dragonegg plugin tries to load LLVMPolly.so plugin...
dyld: lazy symbol binding failed: fast lazy bind offset out of range (39257, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin11.4.2/4.7.2/cc1
dyld: fast lazy bind offset out of range (39257, max=7640) in image
2012 Oct 22
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Sun, Oct 21, 2012 at 06:00:36PM -0700, Nick Kledzik wrote:
> Jack,
>
> Some binary has an initializer which dyld is calling. Somehow the initializer gets to:
> #4 0x0000000100f3b2c0 in Json::Value::maxUInt ()
> which is calling a function in another dylib for the first time. When you call a function in another dylib, you actually jump through a (lazy) pointer. The pointer
2012 Oct 22
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Mon, Oct 22, 2012 at 09:48:59AM -0400, Jack Howarth wrote:
> On Sun, Oct 21, 2012 at 06:00:36PM -0700, Nick Kledzik wrote:
> > Jack,
> >
> > Some binary has an initializer which dyld is calling. Somehow the initializer gets to:
> > #4 0x0000000100f3b2c0 in Json::Value::maxUInt ()
> > which is calling a function in another dylib for the first time. When you
2012 Oct 22
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
Jack,
Some binary has an initializer which dyld is calling. Somehow the initializer gets to:
#4 0x0000000100f3b2c0 in Json::Value::maxUInt ()
which is calling a function in another dylib for the first time. When you call a function in another dylib, you actually jump through a (lazy) pointer. The pointer initially points to a helper which loads an index parameter specifying which function to
2012 Oct 23
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Tue, Oct 23, 2012 at 09:41:46AM +0200, Duncan Sands wrote:
> 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
2012 Oct 23
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Tue, Oct 23, 2012 at 01:05:04PM -0700, Nick Kledzik wrote:
> On Oct 23, 2012, at 12:50 PM, Jack Howarth wrote:
> > On Mon, Oct 22, 2012 at 11:40:32AM -0700, Nick Kledzik wrote:
> >>
> >> On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote:
> >>
> >>> Nick,
> >>> I have uploaded the full walk with 'set env
2012 Oct 23
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Oct 23, 2012, at 1:57 PM, Jack Howarth wrote:
> Nick,
> Can I do this without access to a debug version of dyld? Using the copy of LLVMPolly.so with isl/cloog-isl/gmp statically linked,
> I find that if I set the breakpoint to the address of the initializer...
>
> dyld: calling initializer function 0x100ebb3a0 in /sw/opt/llvm-3.2/lib/LLVMPolly.so
> dyld: lazy symbol binding
2012 Oct 22
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Mon, Oct 22, 2012 at 10:17:56AM -0700, Nick Kledzik wrote:
> 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