Displaying 3 results from an estimated 3 matches for "my_binary".
Did you mean:
macbinary
2020 Apr 18
2
PerfJITEventListener needs perf-<pid>.map?
I'm trying to use PerfJITEventListener with llvm::orc::LLJITBuilder:
1. perf record -o /tmp/perf.data -- <my_binary_with_event_listener>
2. perf inject -j -v -i /tmp/perf.data -o /tmp/perf.data.jit
*jit marker found: ~.debug/jit/llvm-IR-jit-20200417-3c2242/jit-149849.dump*
*injecting: ~/.debug/jit/llvm-IR-jit-20200417-3c2242/jit-149849.dump*
*write ELF image
~/.debug/jit/llvm-IR-jit-20200417-3c2242/jitted-14...
2020 Aug 28
2
End-to-end -fembed-bitcode .llvmbc and .llvmcmd
...s the command line options needed for later compiling that IR to the same native object it was compiled to originally (with the same compiler).
>>
>> Here's what I don't understand: say you have a.o and b.o compiled with -fembed-bitcode=all. They are linked into a binary called my_binary. How do you re-create the corresponding IR for modules a and b (let's call them a.bc and b.bc), and their corresponding command lines? From what I can tell, the linker just concatenates the IR for a and b in my_binary's .llvmbc, and the same for the command line in .llvmcmd. Is there a sepa...
2020 Aug 28
4
End-to-end -fembed-bitcode .llvmbc and .llvmcmd
...needed for
>> later compiling that IR to the same native object it was compiled to
>> originally (with the same compiler).
>>
>> Here's what I don't understand: say you have a.o and b.o compiled with
>> -fembed-bitcode=all. They are linked into a binary called my_binary. How do
>> you re-create the corresponding IR for modules a and b (let's call them
>> a.bc and b.bc), and their corresponding command lines? From what I can
>> tell, the linker just concatenates the IR for a and b in my_binary's
>> .llvmbc, and the same for the comma...