similar to: [LLVMdev] Profiling LLVM JIT code

Hi Priyendra, There is support for oprofile and Intel(r) VTune(tm) Performance Analyzer, but either one needs to be explicitly turned on during the build process. If you use MCJIT (as opposed to the older JIT) then oprofile support isn't in place yet. Both of these work by providing a JITEventListener that receives notification when new code is emitted and hooks it up to the profiling tool

Thanks for the info. I am using old JIT. So that should not be a problem. I will take a look at using oprofile. I have never used it - so will be somewhat of a learning curve. I notice that the configure script has a --with-oprofile option. In addition to enabling that, is there something else that also needs to be done? My copy of LLVM is compiled with --enable-optimized. Will --with-oprofile

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

On Thu, Nov 22, 2012 at 1:53 AM, NAKAMURA 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

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

Hi Alberto, I can confirm the problem you mentioned, and will look at fixing it. You have indeed stumbled on a bug; the two libraries mentioned should only be required if you build with profiling enabled (--enable-intel-jitevents --enable-oprofile flags to configure, or "-DUSE_INTEL_JITEVENTS -DUSE_OPROFILE" flags to cmake.) A workaround, for the time being, would be to ignore those

Olly Betts <olly at survex.com> wrote: > The report you show seems to be just the time take by each function > directly rather than including functions it calls. It looks like a lot > of the time is spent in cursor movement, as totalling up things that > seem like they'd be due to that I quickly get to 40+% but it's hard > to tell if that's about the actual total

Hello Daniel, thank you very much for the clarification. I confirm that the two libraries showed up without specifying the two configure flags. Cheers, Alberto On Fri, Mar 30, 2012 at 8:48 PM, Malea, Daniel <daniel.malea at intel.com> wrote: > Hi Alberto, > > I can confirm the problem you mentioned, and will look at fixing it. You have indeed stumbled on a bug; the two libraries

Catching up on post-holiday emails. I may have comments on the more general stuff later, but wanted to respond to this bit more quickly. On Nov 22, 2012, at 3:05 AM, Chandler Carruth <chandlerc at google.com> wrote: > On Thu, Nov 22, 2012 at 1:53 AM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: >> s/ExecutionEngine/EE/ (or something like buzzword!) > > I don't

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:

We implemented a similar solution for handling crashes in production but one issue we came across with MCJIT was that the NotifyFunctionEmitted call from the old JIT was replaced with NotifyObjectEmitted. The ObjectImage used by NotifyObjectEmitted does have a way of iterating symbols but non-external functions used in the module didn't seem to appear in this list so we were left with some

[Resending this email after subscribing to the group. Got an error message the previous time around] Hey guys, In our project we have the following workflow: - Given a user request, we construct a C++ program to service the request - We create a compiler invocation to compile that program into an IR module - We use JIT (and optionally MCJIT) to convert the IR into executable code and run it

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

Olly Betts <olly at survex.com> wrote: > On Mon, Aug 24, 2020 at 05:58:02AM +0000, Eric Wong wrote: > > Olly Betts <olly at survex.com> wrote: > > > Can prof report time for a function including things it calls? > > > > callgraph? Attached is a profile the output of "perf report -g" > > with callgraph info. I'm no perf expert,

Olly Betts <olly at survex.com> wrote: > On Fri, Aug 21, 2020 at 09:06:59AM +0000, Eric Wong wrote: > > Going back to the "prioritizing aggregated DBs" thread from > > February 2020, I've got 390 Xapian shards for 130 public inboxes > > I want to search against(*). There's more on the horizon (we're > > expecting tens of thousands of public

Hi Andy, In the NotifyObjectEmitted method of our derived JITEventListener class we use the begin_symbol() iterator to walk the object's symbols looking for functions and only functions marked with ExternalLinkage seem to show up. I'm not sure how I would access the Dwarf info from within there, is there a way? Thanks, Andrew On Wed, Nov 13, 2013 at 8:23 PM, Kaylor, Andrew

# Objective Implement an XRay mode 'xray-profiling' that gathers stack trace latencies/durations and builds histograms to provide basic statistics about where time is going in an execution of the application. # Background XRay has two modes currently implemented in compiler-rt: a basic (nee naive) mode and flight data recorder (FDR) mode. Basic mode logging, when enabled, will collect

FYI: Patch is now available for review in https://reviews.llvm.org/D44620. On Thu, Feb 15, 2018 at 1:34 PM Dean Michael Berris <dean.berris at gmail.com> wrote: > # Objective > > Implement an XRay mode 'xray-profiling' that gathers stack trace > latencies/durations and builds histograms to provide basic statistics about > where time is going in an execution of the

Writing your own JITEventListener is probably the best way to capture traces from production. Using the existing gdb/JIT interface support is probably far too heavyweight for production. If you roll your own, you can record the PC ranges efficiently and that should be good enough to capture traces from production. On Tue, Nov 12, 2013 at 2:56 PM, Priyendra Deshwal <deshwal at

I'm asking here, rather than R-devel, because it seems to be a Linux specific question and because I'm using Ubuntu-9.04. I'm trying to profile an package, and got errors, so I decided to follow BDR's (http://tolstoy.newcastle.edu.au/R/devel/06/02/4254.html) example exactly, and got same problem. Can anyone replicate? $ sudo mkdir -p /var/tmp//usr/lib/R/library/stats/libs $