search for: oprofilejiteventlisten

Displaying 4 results from an estimated 4 matches for "oprofilejiteventlisten".

2009 Jul 01
0
[LLVMdev] How to best add a dependency on libopagent.a/so?
...Analysis -lLLVMTarget -lLLVMCore -lLLVMSupport -lLLVMSystem However, this isn't right if we want to build a program like lli: $ g++ ../src/tools/lli/lli.cpp `./Debug/bin/llvm-config --cxxflags --ldflags --libs` -I`pwd`/include /usr/local/google/jyasskin/llvm/oprof/dbg/Debug/lib/libLLVMJIT.a(OProfileJITEventListener.o): In function `(anonymous namespace)::OProfileJITEventListener::NotifyFreeingMachineCode(llvm::Function const&, void*)': /usr/local/google/jyasskin/llvm/oprof/src/lib/ExecutionEngine/JIT/OProfileJITEventListener.cpp:85: undefined reference to `op_unload_native_code' ... (This is th...
2014 Nov 29
2
[LLVMdev] oprofile support?
Mi Maurice, A follow up to Andy's comments: MCJIT can find line numbers for ELF files, at least in limited circumstances. I know because I broke the regression test for it while doing some cleanup recently. ;) Looking at lib/ExecutionEngine/OProfileJIT/OProfileJITEventListener.cpp, I see the line: // TODO: support line number info (similar to IntelJITEventListener.cpp) >From a glance at IntelJITEventListener, I think it would be easy to copy the line number support in there over to OProfileJITEventListener. Cheers, Lang. On Fri, Oct 17, 2014 at 3:04 PM, Kaylor...
2014 Jun 24
2
[LLVMdev] Any way get debug output of generated assembly from MCJIT without completely redoing CodeGen?
Yeah, that's probably how I'd do it. Might be useful if you guys want to contribute that as a command line option Kevin. -eric On Tue, Jun 24, 2014 at 3:03 PM, Kevin Modzelewski <kmod at dropbox.com> wrote: > We do this in Pyston using a JITEventListener that just disassembles the > output; it's "it works let's move on"-quality: >
2014 Oct 17
3
[LLVMdev] oprofile support?
I've been trying to get oprofile results for jitted code without success. I built an 3.5.0 llvm with oprofile enabled, and tested it with lli on a small test case. I built the latest oprofile from the git repository. Debugging I can see that lli is registering the listener and making the oprofile calls to the libopagent api to specify the names and address ranges of jit'd routines, and