Displaying 3 results from an estimated 3 matches for "1216e5f60cd2b23e29856b5227399a".
2017 Oct 11
2
Debugging JIT'ed code with ORC JIT?
...vm-dev <
llvm-dev at lists.llvm.org> wrote:
> That is correct – there is no built-in support. You have to provide your
> own Registrar to the ObjectLinkingLayer to provide this sort of
> functionality. (For example JuliaLang does that at https://github.com/
> JuliaLang/julia/blob/1216e5f60cd2b23e29856b5227399a
> b0f3abef76/src/jitlayers.cpp#L437, in addition to registering the
> function pointer and object file info in several other places).
>
>
> On Sun, Oct 8, 2017 at 11:48 PM Connor Gray via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Hi,
>>
>> I’m...
2017 Oct 07
2
Debugging JIT'ed code with ORC JIT?
Hi,
I’m wondering if it’s possible to debug code JIT’ed with the newer ORC JIT. The LLVM documentation has a page at
llvm.org/docs/DebuggingJITedCode.html <http://llvm.org/docs/DebuggingJITedCode.html>
showing an example of using gdb to debug MCJIT’ed code, but has no mention of ORC JIT.
From searching around online I’ve gotten the impression that ORC JIT does *not* support providing
2017 Oct 11
2
Debugging JIT'ed code with ORC JIT?
...:
> >>
> >> That is correct – there is no built-in support. You have to provide your
> >> own Registrar to the ObjectLinkingLayer to provide this sort of
> >> functionality. (For example JuliaLang does that at
> >> https://github.com/JuliaLang/julia/blob/1216e5f60cd2b23e29856b5227399a
> b0f3abef76/src/jitlayers.cpp#L437,
> >> in addition to registering the function pointer and object file info in
> >> several other places).
> >>
> >>
> >> On Sun, Oct 8, 2017 at 11:48 PM Connor Gray via llvm-dev
> >> <llvm-dev at lists.l...