similar to: Interest in integrating a linux perf JITEventListener?

Displaying 20 results from an estimated 8000 matches similar to: "Interest in integrating a linux perf JITEventListener?"

2017 Feb 02
0
Interest in integrating a linux perf JITEventListener?
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
2016 Dec 29
1
Interest in integrating a linux perf JITEventListener?
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
2018 Mar 26
0
Interest in integrating a linux perf JITEventListener?
Hi, On 2017-02-01 23:20:40 -0800, Andres Freund wrote: > > 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 and in. If it's more complicated, I probably won't have the > > time to assist. > > Patch (and a prerequisite) attached. Took me a while to get
2020 Mar 16
2
ORC JIT Weekly #7 -- JITEventListener support and Swift Immediate Mode Migration
Hi, On 2020-03-09 21:20:44 +0100, Frank Tetzel via llvm-dev wrote: > I think, debugging and profiling support is very important for a JIT > engine. I could never get it to work with older LLVM versions. Is there > example code somewhere available? Since I added the perf listener I probably can help you with that. What exactly was the problem you were hitting? I don't have isolated
2020 Mar 09
4
ORC JIT Weekly #7 -- JITEventListener support and Swift Immediate Mode Migration
Hi All, Just a couple of updates this week: First: there is a preview patch up at https://reviews.llvm.org/D75838 to enable use of JITEventListeners in RTDyldObjectLinkingLayer. I've only done very preliminary testing on it, but was able to debug simple JIT'd programs on Linux using the GDB registration listener. If you've been wanting to move to ORC but held up by lack of debugger /
2017 Mar 08
2
ORC C Interface & JITEventListeners
Hi, I am working on using LLVM to compile parts of longrunning PostgreSQL queries into native code for faster code execution. As postgres is, nearly, entirely written in C and has long-lived (5 years) supported branches (making the higher API stability important), I'm currently using the C API. I started out using MCJIT but it looks like that's slowly on the way out. My current concern
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
2018 Jul 24
3
profiling JIT compiled code with perf
Hi, On 2018-07-19 14:57:42 +0200, Frank Tetzel via llvm-dev wrote: > > Have you seen https://reviews.llvm.org/D44892? we are using it in > > Julia to use perf on jitted code. > > No, I did not see this patch before. Thanks a lot for the pointer. > > It seems to be doing exactly what I want. Let's see if I get it working. FWIW, I just merged this. Did you have any
2012 May 24
1
[LLVMdev] JITEventListener destructor location
Hello, I've recently finished moving a cross-platform project to LLVM 3.0 and now transitioning to 3.1. One of the things I've hit is on OS X, I have linker errors involving JITEventListener and I've noticed if I move the JITEventListener destructor out of JIT.cpp and into JITEventListener.h (like other functions of JITEventListener), the linker is much happier. I'd like to push
2018 Jul 19
2
profiling JIT compiled code with perf
Have you seen https://reviews.llvm.org/D44892? we are using it in Julia to use perf on jitted code. -Valentin On Wed, 18 Jul 2018 at 17:13 Frank Tetzel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Hello, > > > > is there any support in LLVM for the jitdump format [1] of perf? > > > > It enables perf report to also "zoom in" and annotate the
2020 Mar 16
4
ORC JIT Weekly #8: Basic OrcV2 C Bindings, MachO and COFF improvements.
Hi All, I've added a very basic set of C bindings for OrcV2 in 633ea07200e, with an example in llvm/example/OrcV2Examples/BasicOrcV2CBindings. Development of the C APIs is being tracked by http://llvm.org/PR31103 -- if you're interested in C APIs for OrcV2 please get involved. I would especially appreciate feedback and patches from C API users: I don't have a use case for the C APIs
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
2020 Mar 31
2
ORC JIT Weekly #7 -- JITEventListener support and Swift Immediate Mode Migration
> Last time I tried it was some months ago with LLVM 9. I'll try it > shortly with LLVM trunk/master and report back. Finally, I found the time to try it out again. And it works fine in LLVM master. I haven't tried any other LLVM version. Profiling with perf on assembly level works fine. And so does gdb. One can set pending breakpoints on the to be generated function and execution
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 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
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
2017 Jan 24
3
[InstCombine] rL292492 affected LoopVectorizer and caused 17.30%/11.37% perf regressions on Cortex-A53/Cortex-A15 LNT machines
On Tue, Jan 24, 2017 at 1:20 PM, Sanjay Patel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > I started looking at the log files that you attached, and I'm confused. > The code that is supposedly causing the perf regression is created by the > loop vectorizer, right? Except the bad code is not in the "vector.body", so > is there something peculiar about
2018 Nov 15
2
[RFC][llvm-mca] Adding binary support to llvm-mca.
Introduction ----------------- Currently llvm-mca only accepts assembly code as input. We would like to extend llvm-mca to support object files, allowing users to analyze the performance of binaries. The proposed changes (which involve both clang and llvm) optionally introduce an object file section, but this can be stripped-out if desired. For the llvm-mca binary support feature to be useful, a
2020 Sep 26
3
LLVM Developers Meeting JIT BoF -- Request for Topics of Interest
Hi All, The 2020 Virtual LLVM Developer's Meeting is coming up the week after next. I'll be hosting a JIT Birds-of-a-Feather session on Thursday the 8th at 10:55am PDT (See http://llvm.org/devmtg/2020-09/schedule/). I'm planning to run this more like a Round Table: Minimal introduction, plenty of time for discussion. Does anyone have any LLVM JIT related topics that they would
2020 Sep 28
2
LLVM Developers Meeting JIT BoF -- Request for Topics of Interest
Hi Andres, A topic that I'd find interesting is what it'd take to make it easier to > use profile guided optimization in the context of JIT. A few years back > I crudely hacked this together, but it was fairly ugly. It'd be nice to > make that easier. Possibly too complicated for that type of session? We couldn't go into detail, but we could kick off a discussion and