Displaying 9 results from an estimated 9 matches for "weisse4".
2013 Apr 09
2
[LLVMdev] Migration from JIT to MCJIT
...ates in memory, mostly using the llvm-c api, and then runs the generated code.
When I try to use MCJIT I encounter a problem with relocations of external symbols – functions compiled statically beforehand with gcc.
I get the following error:
Invalid relocation type!
UNREACHABLE executed at /Users/weisse4/dev/llvm/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldMachO.cpp:89
While debugging, I see that the relocation type read in RuntimeDyldImpl::loadObject is 218103811, which seems corrupt to me.
Did someone encounter a similar error? Or can direct me to changes that I need to do while migrating fr...
2013 Apr 09
0
[LLVMdev] Migration from JIT to MCJIT
...d then runs
> the generated code.
> When I try to use MCJIT I encounter a problem with relocations of
> external symbols -- functions compiled statically beforehand with gcc.
>
> I get the following error:
>
> Invalid relocation type!
> UNREACHABLE executed at
> /Users/weisse4/dev/llvm/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldMachO.cpp:89
>
> While debugging, I see that the relocation type read in
> RuntimeDyldImpl::loadObject is 218103811, which seems corrupt to me.
Hi Weiss,
I do not have any experience on Mach binary format, but the hex
value...
2013 Apr 10
2
[LLVMdev] Migration from JIT to MCJIT
...ates in memory, mostly using the llvm-c api, and then runs the generated code.
When I try to use MCJIT I encounter a problem with relocations of external symbols – functions compiled statically beforehand with gcc.
I get the following error:
Invalid relocation type!
UNREACHABLE executed at /Users/weisse4/dev/llvm/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldMachO.cpp:89
While debugging, I see that the relocation type read in is 218103811, which seems corrupt to me.
Hi Weiss,
I do not have any experience on Mach binary format, but the hex value of 218103811 is 0xd000003 (maybe the reloca...
2013 Apr 10
0
[LLVMdev] Migration from JIT to MCJIT
...ates in memory, mostly using the llvm-c api, and then runs the generated code.
When I try to use MCJIT I encounter a problem with relocations of external symbols – functions compiled statically beforehand with gcc.
I get the following error:
Invalid relocation type!
UNREACHABLE executed at /Users/weisse4/dev/llvm/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldMachO.cpp:89
While debugging, I see that the relocation type read in is 218103811, which seems corrupt to me.
Hi Weiss,
I do not have any experience on Mach binary format, but the hex value of 218103811 is 0xd000003 (maybe the reloca...
2013 Apr 10
2
[LLVMdev] Migration from JIT to MCJIT
...llvm-c api, and then runs the generated code.
> When I try to use MCJIT I encounter a problem with relocations of external symbols – functions compiled statically beforehand with gcc.
>
> I get the following error:
>
> Invalid relocation type!
> UNREACHABLE executed at /Users/weisse4/dev/llvm/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldMachO.cpp:89
>
> While debugging, I see that the relocation type read in is 218103811, which seems corrupt to me.
>
> Hi Weiss,
>
> I do not have any experience on Mach binary format, but the hex value of 218103811...
2013 Apr 11
2
[LLVMdev] Migration from JIT to MCJIT
...ates in memory, mostly using the llvm-c api, and then runs the generated code.
When I try to use MCJIT I encounter a problem with relocations of external symbols – functions compiled statically beforehand with gcc.
I get the following error:
Invalid relocation type!
UNREACHABLE executed at /Users/weisse4/dev/llvm/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldMachO.cpp:89
While debugging, I see that the relocation type read in is 218103811, which seems corrupt to me.
Hi Weiss,
I do not have any experience on Mach binary format, but the hex value of 218103811 is 0xd000003 (maybe the reloca...
2013 Apr 11
0
[LLVMdev] Migration from JIT to MCJIT
...ates in memory, mostly using the llvm-c api, and then runs the generated code.
When I try to use MCJIT I encounter a problem with relocations of external symbols – functions compiled statically beforehand with gcc.
I get the following error:
Invalid relocation type!
UNREACHABLE executed at /Users/weisse4/dev/llvm/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldMachO.cpp:89
While debugging, I see that the relocation type read in is 218103811, which seems corrupt to me.
Hi Weiss,
I do not have any experience on Mach binary format, but the hex value of 218103811 is 0xd000003 (maybe the reloca...
2013 Apr 11
0
[LLVMdev] Migration from JIT to MCJIT
...ates in memory, mostly using the llvm-c api, and then runs the generated code.
When I try to use MCJIT I encounter a problem with relocations of external symbols – functions compiled statically beforehand with gcc.
I get the following error:
Invalid relocation type!
UNREACHABLE executed at /Users/weisse4/dev/llvm/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldMachO.cpp:89
While debugging, I see that the relocation type read in is 218103811, which seems corrupt to me.
Hi Weiss,
I do not have any experience on Mach binary format, but the hex value of 218103811 is 0xd000003 (maybe the reloca...
2013 Apr 11
2
[LLVMdev] Migration from JIT to MCJIT
...ates in memory, mostly using the llvm-c api, and then runs the generated code.
When I try to use MCJIT I encounter a problem with relocations of external symbols – functions compiled statically beforehand with gcc.
I get the following error:
Invalid relocation type!
UNREACHABLE executed at /Users/weisse4/dev/llvm/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldMachO.cpp:89
While debugging, I see that the relocation type read in is 218103811, which seems corrupt to me.
Hi Weiss,
I do not have any experience on Mach binary format, but the hex value of 218103811 is 0xd000003 (maybe the reloca...