search for: dibyendumajumdar

...test that one can look in isolation. I am working on building a JIT compiler for Lua (actually a derivative of Lua). It is currently work in progress. The approach is to compile Lua bytecodes into LLVM IR. The IR generated from my code is here (after optimization I should add): https://github.com/dibyendumajumdar/ravi/blob/master/clang-output/lua_op_loadk_return_ravi.ll I am using the output from Clang as a guide to generating IR. So I write small snippets of code in C which are equivalent to Lua bytecodes - then use Clang to emit the IR. I use this to work out the IR I need to build. The C equivalent of...

...> Could you please send me your unoptimized and expected optimized code? The default implementation only contains some transformations. It would be helpful to know what you are actually trying. > Optimize Module is just a function object. > You can view the code here: https://github.com/dibyendumajumdar/ravi/blob/master/include/ravi_llvmcodegen.h https://github.com/dibyendumajumdar/ravi/blob/master/src/ravi_llvmjit.cpp Just look for USE_ORCv2_JIT The code is messy but that is because LLVM's api keeps changing from version to version, causing huge issues for users. > > On Sat, 10 Aug...

...eading. I figured out below which was part of the problem. Code is still not getting optimized at all. I don't really know what is going on. Yet the same setup works fine with the Legacy ORC v1 setup. Any help is appreciated. Here are again the links to the relevant code: https://github.com/dibyendumajumdar/ravi/blob/master/include/ravi_llvmcodegen.h https://github.com/dibyendumajumdar/ravi/blob/master/src/ravi_llvmjit.cpp Just look sections marked USE_ORCv2_JIT. >> > Optimize Module is just a function object. >> > >> >> Thank you - I fixed that now. Regards Dibyendu

Hi, I wrote sometime ago about this issue (see links below). http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-March/084089.html http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-April/084193.html At the time I thought the problem was due to a bug in my code, and that I had fixed it. But sadly it seems that the issue is still present - it just got hidden by whatever change I made. The error only

If you could create a single executable with a repro, and publish them somewhere (both the old llvm and new one which is slower), we could look at it. It's hard to say otherwise unless someone truly knows of a change. I'm interested in looking at this, because my experience has been opposite, compile times improved for my compiler in the past month. So I'm inclined to understand what

...ny followups would be helpful. On Sat, Apr 25, 2015 at 3:07 PM, Dibyendu Majumdar <mobile at majumdar.org.uk> wrote: > I have an example test program (smallest I could construct) that > triggers the problem. The relevant line is commented in the code. > > > https://github.com/dibyendumajumdar/ravi/tree/master/ravi-tests/longjmp_issue > > I have also dumped the IR for the three functions that are compiled. > > The C code that does the longjmp and setjmp is at: > > https://github.com/dibyendumajumdar/ravi/blob/master/src/ldo.c > > See functions luaD_throw() and lua...

Hi, I am using the LLVM release_37 branch and have a strange issue. Please see the two IR outputs I have saved below: https://github.com/dibyendumajumdar/ravi/tree/master/ravi-tests/comp_issue The original.ll is the code I am generating. The aftercompiling.ll is the output from LLVM with opt level 0. The issue is that LLVM is deciding to remove the blocks with labels updatei and updatei.64 (lines 433 and 454 in original.ll) for some reason that I...

On 22 February 2015 at 22:54, Hal Finkel <hfinkel at anl.gov> wrote: >> I tried setting the module's DataLayout to the engine's DataLayout. >> Don't see any improvement. >> The memcpy() is to perform a struct assign, so I tried replacing that >> with member by member store. >> But even then the loads are not being eliminated so I guess the >>

On Sat, 10 Aug 2019 at 21:05, Praveen Velliengiri <praveenvelliengiri at gmail.com> wrote: > > Optimize Module is just a function object. > Thank you - I fixed that now. Regards

Hi, I am trying out ORC v2 and facing some problems. I am using LLVM 8.0.1. I updated my ORC v1 implementation from 6.0 to 8.0 based on Kaleidoscope example (i.e. using Legacy classes) and that works fine. Now I am trying out ORC v2 apis, based on https://github.com/llvm-mirror/llvm/blob/master/examples/Kaleidoscope/BuildingAJIT/Chapter2/KaleidoscopeJIT.h. I have got it to compile and build.