Displaying 4 results from an estimated 4 matches for "lp_bld_debug".
2014 May 22
4
[LLVMdev] perf tool support in MCJIT
I believe the perf tool cannot profile/analyze the JITed code in MCJIT
model.
Can you please confirm this ? I was working on a patch to fix this.
Another question, is the there any support to map the llvm IR with x86
generated assembly ? so its easier to analyze the code generator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2014 Apr 25
4
[LLVMdev] Drop the machine code while executing
Hi
Currently , I have doing some experimental work by using llvm,
Is it possible to drop the machine code once it has been generated for
particular function while program executing. For example some *void
test(int)* function has been executed on native machine , I want to drop
the code before I start execute some other function in my long running
program.
Thanks.
With regards
Sri.
2012 Mar 01
2
[LLVMdev] Is there any way to print assembly code of a function compiled by ExecutionEngine?
Hello!
I'm using LLVM's JIT in my project. Is there any way to view assembly
code of functions it generates without disassembling them from the
memory?
2017 Aug 21
20
[Bug 102349] New: nv4x crashing with plasmashell - gdb log included
...ibrary "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe2cfa700 (LWP 5161)]
[New Thread 0x7fffe208d700 (LWP 5165)]
[New Thread 0x7fffe1051700 (LWP 5174)]
[New Thread 0x7fffd2f5f700 (LWP 5175)]
[New Thread 0x7fffd10f4700 (LWP 5176)]
warning: Could not find DWO CU
gallivm/.libs/lp_bld_debug.dwo(0x705e1d0e169ca1fe) referenced by CU at offset
0x14078a9 [in module
/usr/lib/debug/.build-id/62/a543423306e4787e29a78fbd94c9a2cdf8ff3d.debug]
warning: Could not find DWO CU
gallivm/.libs/lp_bld_misc.dwo(0x3f68ad1a054cd591) referenced by CU at offset
0x1422424 [in module
/usr/lib/debug/.build-id...