Displaying 3 results from an estimated 3 matches for "4b975fa9".
2018 Jan 19
1
[JIT] Evaluating Debug-Metadata in bitcode
...LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180119/4b975fa9/attachment-0001.html>
2018 Jan 19
0
[JIT] Evaluating Debug-Metadata in bitcode
Hi Björn,
I'm not sure I understand what you are actually trying to achieve.
Do you want to be able to debug from your main code, and step into the
JITed code?
Do you want to be able to set breakpoints, list callstacks, etc in the
JITed code?
Do you want to, from a crash, identify where in your JITed code it went
wrong?
The first two are definitely one or more order(s) of magnitude harder
2018 Jan 19
3
[JIT] Evaluating Debug-Metadata in bitcode
Hello LLVM-People,
I'm still a beginner with the LLVM, but I really like the concept and the
possibilities with the JIT.
Currently I compile simple functions with clang-cl into bitcode files.
After this I use another program to JIT this bitcode files and execute
functions of it - like lli.
Thanks to a lot of mails and so on, I understood that a bitcode file is in
fact still IR-Code, but