Displaying 6 results from an estimated 6 matches for "jitsymbolentri".
Did you mean:
jitsymbolentry
2009 Jun 24
3
[LLVMdev] [llvm-commits] JITEventListener for eventual profiling and maybe gdb support
Hi Jeffrey,
This looks very good. Thanks. Some comments:
+/// JitSymbolEntry - Each function that is JIT compiled results in
one of these
+/// being added to an array of symbols. This indicates the name of
the function
+/// as well as the address range it occupies. This allows the client
to map
+/// from a PC value to the name of the function.
+struct JitSymbolEntry {
A nitpick. Please
2009 Jun 25
0
[LLVMdev] [llvm-commits] JITEventListener for eventual profiling and maybe gdb support
On Wed, Jun 24, 2009 at 2:43 PM, Evan Cheng<evan.cheng at apple.com> wrote:
> Hi Jeffrey,
>
> This looks very good. Thanks. Some comments:
>
> +/// JitSymbolEntry - Each function that is JIT compiled results in
> one of these
> +/// being added to an array of symbols. This indicates the name of
> the function
> +/// as well as the address range it occupies. This
2009 Jun 24
0
[LLVMdev] JITEventListener for eventual profiling and maybe gdb support
Ack, sorry. I should have sent this to llvm-commits instead. :-P
Followups there please.
On Wed, Jun 24, 2009 at 12:02 PM, Jeffrey Yasskin<jyasskin at google.com> wrote:
> I intend to use this to support oprofile's ability to symbolize JITted
> code through the interface described at
> http://oprofile.sourceforge.net/doc/devel/jit-interface.html. I
> believe the interface
2009 Jun 24
2
[LLVMdev] JITEventListener for eventual profiling and maybe gdb support
I intend to use this to support oprofile's ability to symbolize JITted
code through the interface described at
http://oprofile.sourceforge.net/doc/devel/jit-interface.html. I
believe the interface will also be useful for gdb support. I'm
considering adding some flags to the JITEventListener to let the JIT
avoid collecting information no listener is going to use, but I won't
do that
2009 Jan 27
1
[LLVMdev] Newbie question: Getting info about JIT-compiled function
Apologies if this is a FAQ.
I am using the LLVM JIT facility on an x86_64 platform. I generate IR for a single function using IRBuilder(), use the FunctionPassManager to do some optimization passes, and then call ExecutionEngine::getPointerToFunction() to get a native-code version of the function. Everything works fine so far.
Two questions:
Question (1): How can I get the size of the native
2009 Jan 28
1
[LLVMdev] Newbie question: Getting info about JIT-compiled function
Andrew Haley wrote:
> Jeff Kuskin wrote:
> > Apologies if this is a FAQ.
> >
> > I am using the LLVM JIT facility on an x86_64 platform. I generate
> > IR for a single function using IRBuilder(), use the
> > FunctionPassManager to do some optimization passes, and then call
> > ExecutionEngine::getPointerToFunction() to get a native-code version
> > of