search for: javajit

Hello i noticed that in revision 159659 some paths have changed a patch: sed 's|llvm/Analysis/DIBuilder.h|llvm/DIBuilder.h|g' lib/j3/Compiler/JavaLLVMCompiler.cpp lib/j3/Compiler/JavaJIT.cpp sed 's|llvm/Analysis/DebugInfo.h|llvm/DebugInfo.h|g' lib/j3/Compiler/JavaJIT.cpp lib/j3/Compiler/JavaJIT.h lib/j3/Compiler/JavaJITCompiler.cpp lib/vmkit/Compiler/JIT.cpp Foivos

...llvm[4]: Building Release+Asserts Archive Library libClasspath.a make[4]: Leaving directory `/home/chris/vmkit/lib/j3/ClassLib/GNUClasspath' make[3]: Leaving directory `/home/chris/vmkit/lib/j3/ClassLib' make[3]: Entering directory `/home/chris/vmkit/lib/j3/Compiler' llvm[3]: Compiling JavaJIT.cpp for Release+Asserts build (bytecode) warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Wunknown-warning-option] JavaJIT.cpp:1262:23: error: no member named 'removeFnAttr' in 'llvm::Function' llvmFunctio...

...elease+Asserts Archive Library libClasspath.a > make[4]: Leaving directory `/home/chris/vmkit/lib/j3/ClassLib/GNUClasspath' > make[3]: Leaving directory `/home/chris/vmkit/lib/j3/ClassLib' > make[3]: Entering directory `/home/chris/vmkit/lib/j3/Compiler' > llvm[3]: Compiling JavaJIT.cpp for Release+Asserts build (bytecode) > warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean > '-Wno-uninitialized'? [-Wunknown-warning-option] > JavaJIT.cpp:1262:23: error: no member named 'removeFnAttr' in > 'llvm::Function'...

...rch). For the moment, you should use the VMKit2 > repository as it's probably the most advanced one. Hi Gael, does it mean vmkit will based on the latest llvm after the merge finished? I run into the same issue Chris meet when trying to verify tilegx backend by compiling vmkit. JavaJIT.cpp:1262:23: error: no member named 'removeFnAttr' in 'llvm::Function' llvmFunction->removeFnAttr( then I change to vmkit2, but found it's based on 3.2 only, failed compile with latest llvm > > See you, > Gaël > > > > 2013/2/24 Minas Abr...

Hi, I am wondering how I can get the JIT'd llvm IR during VMKit execution. I am stuck in precompiling phase (when loading library classes), and I am facing various problems. If I can log the JIT'd llvm IR (from Java bytecode), that would be convenient. I turned on --enable-debug, but it doesn't seem very helpful at this stage. Any other suggestion is welcome. Thanks very much.

Duncan Sands wrote: >> One approach would be to simply duplicate the code in the 'finally' >> block for each exit, but that seems sub-optimal. It would be better, I >> think, to set a state variable before entering the 'finally' block, and >> then have it do a switch instruction at the end and transfer to the >> appropriate block. >>

Hi Minas, Basically, you should not have any difference between the two projects :) (it's not really the case, but we are working on this problem). To explain (sorry for my long email!), I work for a french research institution (Inria) and, as we have an Inria research project around VMKit, I had to create a repository inside my institution (a researcher has always to make his institution

Hi Harris, A question has arisen, what is the difference between VMKit2 and VMKit, and why, in the first place the new VMKit2 fork was been created? Thanks for answer :) Best regards, Minas On Tue, Feb 12, 2013 at 2:36 PM, Harris Bakiras <h.bakiras at gmail.com> wrote: > Hi Chris, > > For the moment you can install VMKit following these instructions: > >

Can you point out to me where in the VMKit code I should be looking? I spent some additional time reading the docs, and I have some specific questions: 1) I'm trying to figure out the relationship between the __cxa_throw function, and the _Unwind_RaiseException function mentioned in the ABI doc. My guess is that _Unwind_RaiseException is the language-neutral implementation of stack unwinding,