search for: jiter

i want to integrate a C source JITer into my application but the resulting executables are too large is it possible to reduce the resulting libs/exe some way? current VS2017/svn build example: llvm-build\Release\bin\clang-interpreter.exe ~36MB for now (that can change later) - i want to jit simple c-code - no std library or someth...

...david told, you can make the symbols of your host process visible to the JIT'd code through DynamicLibrarySearchGenerator::getForCurrentProcess. On Thu, 19 Sep 2019 at 00:46, David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > +Lang Hames <lhames at gmail.com> , JITer of JITs. > > I believe there's some kind of resolver you can add that finds symbols in > the current process. Yes, lli uses some of the same pieces of JIT > infrastructure so you could go look at its source code to see how it's > managing this. > > On Wed, Sep 18, 2019...

...y, win64 version of compilation callback function should be added, otherwise you'll quickly result to messed stack, invalid incoming args, etc (this can be exactly your case now, btw). Also, I think that you should carefully inspect, what to save there, because you will 'mix' two CCs: JITer itself will be compiled with win64 CC and function JITed with normal x86-64 CC and they shouldn't trash the states of each other during crossing of 'CC border'. -- WBR, Anton Korobeynikov

When I declare some functions in my IR code which belongs to the C standard library(printf for example), the JIT will report that symbol cannot found. So is there any way I can add these libraries to my JIT? P.S. When I using lli, the printf will work, I guess lli is a JIT(right?) and it somehow knows where to find the symbol printf -------------- next part -------------- An HTML attachment was

...hat you're using SelectionDAGISel for static compilation and FastISel for JIT compilation. The latter generated code very quickly, as the name implies, but the quality of that code is generally pretty terrible compared to the static compiler. > Is there an option that I can pass to the (MC)JITer to force it to use SelectionDAGISel? I'm also curious which passes/algorithms are used when I set the MCJIT option to true and the opt level to Aggressive. E.g: engineBuilder.setUseMCJIT(true); engineBuilder.setOptLevel(llvm::CodeGenOpt::Aggressive); I adapted lli.cpp to use MCJIT in my...

On Oct 12, 2012, at 11:14 AM, Baris Aktemur <baris.aktemur at ozyegin.edu.tr> wrote: > > On 12 Eki 2012, at 20:00, Jim Grosbach wrote: > >> >> On Oct 12, 2012, at 7:07 AM, Baris Aktemur <baris.aktemur at ozyegin.edu.tr> wrote: >> >>> Dear Tim, >>> >>>> >>>> The JIT sounds like it does almost exactly what you

Hello, i want to install ocfs2-tools-1.2.0-1 on slackware 10.2 (up-to-date) with 2.6.17.2 kernel and i got error: ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no

Hello, i want to install ocfs2-tools-1.2.0-1 on slackware 10.2 (up-to-date) with 2.6.17.2 kernel and i got error: ./configure checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no

On 12 Eki 2012, at 20:00, Jim Grosbach wrote: > > On Oct 12, 2012, at 7:07 AM, Baris Aktemur <baris.aktemur at ozyegin.edu.tr> wrote: > >> Dear Tim, >> >>> >>> The JIT sounds like it does almost exactly what you want. LLVM's JIT >>> isn't a classical lightweight, dynamic one like you'd see for >>> JavaScript or Java.

Dear Sir/Madam Our company, 4Js software, has developed an SQL data base software that runs under different operating systems: Windows, Linux, Mac OS X. This software compiles each SQL statement into a C program that is compiled "on the fly" and executed by our JIT, Just In Time compiler. We wanted to port it to Apple's iOS, and spent a lot of time retargetting the JIT for