search for: oprofilejit

Hi all, I am experiencing a problem with the libraries IntelJITEvents and OProfileJIT They are listed in the `llvm-config --libs all` output but they are not present in the lib install directory. I am using git, revision 153741. Am I missing something ? Is this a known issue ? Thanks, Alberto

...o ignore those two missing libraries. Thanks, Dan -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Alberto Magni Sent: Friday, March 30, 2012 11:36 AM To: LLVM Developers Mailing List Subject: [LLVMdev] Missing IntelJITEvents and OProfileJIT libs Hi all, I am experiencing a problem with the libraries IntelJITEvents and OProfileJIT They are listed in the `llvm-config --libs all` output but they are not present in the lib install directory. I am using git, revision 153741. Am I missing something ? Is this a known issue ? Thanks, Albe...

...> Thanks, > Dan > > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Alberto Magni > Sent: Friday, March 30, 2012 11:36 AM > To: LLVM Developers Mailing List > Subject: [LLVMdev] Missing IntelJITEvents and OProfileJIT libs > > Hi all, > > I am experiencing a problem with the libraries IntelJITEvents and OProfileJIT They are listed in the `llvm-config --libs all` output but they are not present in the lib install directory. > I am using git, revision 153741. > > Am I missing something ? Is th...

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: >

...A Takumi <geek4civic at gmail.com> wrote: > s/ExecutionEngine/EE/ (or something like buzzword!) I don't really know the best bikeshed color here. Jim? My lame idea would be: ExecutionEngine -> JIT ExecutionEngine -> JIT/Legacy ExecutionEngine/MCJIT -> JIT/MC ExecutionEngine/OProfileJIT -> JIT/OProfile ExecutionEngine/IntelJITEvenst -> JIT/IntelJITEvents ExecutionEngine/RuntimeDyld -> JIT/RuntimeDyld (maybe RuntimeDyld -> DynamicLoader ? Too direct?) But not sure this is really an accurate model for the logical layering of these libraries?

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:

...ew code is emitted and hooks it up to the profiling tool via some tool-specific notification API. I'm not familiar with pprof, but it probably wouldn't be very difficult to write a new event listener to add support for pprof. You can find the oprofile code in 'llvm/lib/ExecutionEngine/OProfileJIT' to use as an example. -Andy From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Priyendra Deshwal Sent: Sunday, March 03, 2013 3:11 AM To: llvmdev at cs.uiuc.edu Subject: [LLVMdev] Profiling LLVM JIT code Hey guys, I am currently working on a project t...

...gt;> s/ExecutionEngine/EE/ (or something like buzzword!) > > I don't really know the best bikeshed color here. Jim? > > My lame idea would be: > > ExecutionEngine -> JIT > ExecutionEngine -> JIT/Legacy > ExecutionEngine/MCJIT -> JIT/MC > ExecutionEngine/OProfileJIT -> JIT/OProfile > ExecutionEngine/IntelJITEvenst -> JIT/IntelJITEvents > ExecutionEngine/RuntimeDyld -> JIT/RuntimeDyld > So long as we have the interpreter, we should keep the ExecutionEngine abstraction around. That said, I'd personally like to kill the interpreter… Eventu...

Hey guys, I am currently working on a project that uses JIT compilation to compile incoming user requests to native code. Are there some best practises related to profiling the generated code? My project uses gperftools pprof for profiling etc. Is there a way to hook the two up? Are there any other profiling method that works? This page describes how to debug JIT code with GDB. I wonder if

...up to the profiling tool > via some tool-specific notification API. I’m not familiar with pprof, but > it probably wouldn’t be very difficult to write a new event listener to add > support for pprof.**** > > ** ** > > You can find the oprofile code in ‘llvm/lib/ExecutionEngine/OProfileJIT’ > to use as an example.**** > > ** ** > > -Andy**** > > ** ** > > *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] *On > Behalf Of *Priyendra Deshwal > *Sent:* Sunday, March 03, 2013 3:11 AM > *To:* llvmdev at cs.uiuc.edu > *Subj...

...PERF ) > + > set(LLVM_USE_SANITIZER "" CACHE STRING > "Define the sanitizer used to build binaries and tests.") > > @@ -638,6 +648,9 @@ endif (LLVM_USE_INTEL_JITEVENTS) > if (LLVM_USE_OPROFILE) > set(LLVMOPTIONALCOMPONENTS ${LLVMOPTIONALCOMPONENTS} OProfileJIT) > endif (LLVM_USE_OPROFILE) > +if (LLVM_USE_PERF) > + set(LLVMOPTIONALCOMPONENTS PerfJITEvents) > +endif (LLVM_USE_PERF) > > message(STATUS "Constructing LLVMBuild project information") > execute_process( > diff --git a/include/llvm/Config/config.h.cmake b/i...

Having something like this available in tree would definitely be useful. For simplicity, why don't we start with support for the second style? This is the long term useful one and would be a good starting point for getting the code in tree. Can you give a pointer to the patch so that I can assess the rough complexity? If it's simple enough, I'd be happy to help get it reviewed

Hi, On 2016-12-29 13:17:50 -0800, Philip Reames wrote: > Having something like this available in tree would definitely be > useful. Cool. > For simplicity, why don't we start with support for the second style? This > is the long term useful one and would be a good starting point for getting > the code in tree. Works for me. > Can you give a pointer to the patch so that

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,...

2012/11/22 Chandler Carruth <chandlerc at google.com>: > Hello LLVM & Clang hackers! > > Based on a discussion with Chris, I would like to propose a Great > Renaming of Things for the 3.3-era LLVM and Clang codebase. > > First and foremost, the two most significant changes I would like to make: > > 1) llvm/lib/VMCore/... -> llvm/lib/IR/... > > I've

Hello LLVM & Clang hackers! Based on a discussion with Chris, I would like to propose a Great Renaming of Things for the 3.3-era LLVM and Clang codebase. First and foremost, the two most significant changes I would like to make: 1) llvm/lib/VMCore/... -> llvm/lib/IR/... I've discussed potential names for the VMCore (or LLVMCore) library with lots of folks, and the best idea anyone

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