search for: tetzel

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 JIT compiled > > code on assembly level with r...

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

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 /

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

Hi all, I open sourced a small project of mine recently. It is an EDSL for C++ which makes just-in-time compilation much easier to write and maintain. One of its backends is LLVM's OrcJIT (LLVM 7, still). https://github.com/tetzank/coat Here is a blog post of mine introducing the concept: https://tetzank.github.io/posts/coat-edsl-for-codegen/ You can see it as an abstraction layer on top

> 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

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 JIT compiled code on assembly level with runtime percentage. It helps a lot to understand which parts of the generated code is the bottleneck. I recently did a proof-of-concept for the JIT assembler asmjit [2]. It just dumps the generated code in the right

Using llvm 9, visual studio, HowToUseLLJIT.cpp It works fine in a release build. In a debug build It aborts due to an assert failure on Core.cpp (383) because the lhs flags are (Exported | Callable) and the rhs flags are (Callable). What mods should be made to fix this issue? Side note: The comments at the top reference HowToUseJIT.cpp rather than HotToUseLLJIT.cpp Thanks, Rob Conde

Hello LLVM developers, I am developing a small project using LLVM. The objective is to provide dynamic loading via JIT compilation of C++ code contained in a (TS) module. For this reason, I would like to return an explicitly raw void pointer (resembling libdl's `void *dlsym(void *, char const *);` as closely as possible) to the compiled result. The MCJIT class offers the most convenient API

Hi Geoff, hi Alex If you implement the GDB JIT Interface in your Orc JIT, this is in general possible (at least from the JIT's point of view) with both debuggers, GDB and LLDB. Please have a look at the example here: https://github.com/weliveindetail/JitFromScratch/tree/jit-debug/gdb-interface You will probably need to adjust the code depending on the LLVM version you are using. As described