search for: ladyvm

...showed that is almost entirely due to the llvm instruction selector (The register allocator and optimisation passes are fast) The split in execution time for JIT compilation being approximately: (My) IR code generation: 1 (llvm) Register allocation: 1 (llvm) Instruction selection: 12 The ladyvm JVM paper noted the same problem: http://vmkit.llvm.org/ladyvm.html So I did a quick experiment with llvm and lcc (http://www.cs.princeton.edu/software/lcc), in order to see how much faster instruction selection could be. lcc uses a BURG-type (called lburg) instruction-selector. The following...

...a few dependency problems). After compiling a simple HelloWorld with javac I got ../vmkit/Debug/bin/jnjvm HelloWorld hang for a while and then spits out a terminate called without an active exception Abort I also tried to compile on a machine with gcc 4.1 and Instead I got jnjvm: /mnt/sdb1/ladyvm/vmkit/include/mvm/VirtualMachine.h:369: T* mvm::VirtualMachine::IPToMethod(void*) [with T = jnjvm::JavaMethod]: Assertion `I != Functions.begin() && "Wrong value in function map"' failed. Aborted A friend of mine tried the build process on his machine and got the same...

...lasspath shared libraries misinstalled. Have you done the links from procedure no 2 on the "get started" page? It can also be due to x86_64/x86_32 compatibility issues. Is that the case? > I also tried to compile on a machine with gcc 4.1 and Instead I got > > jnjvm: /mnt/sdb1/ladyvm/vmkit/include/mvm/VirtualMachine.h:369: T* > mvm::VirtualMachine::IPToMethod(void*) [with T = jnjvm::JavaMethod]: > Assertion `I != Functions.begin() && "Wrong value in function map"' > failed. > Aborted > > A friend of mine tried the build process on h...

...using here? I'm using 2.4 My original time ratios of reg-alloc to instruction selection (1:12) referred to the local register allocator and the standard instruction selector (all passes), not a sensible comparison, I realise. > I did some benchmarks in vmkit (the project that encompass ladyvm) and > compilation time is roughly 50% faster with both fast and local register > allocator. Choosing the fast selector does speed code-generation by almost double, when using llc, but the reduction in final code speed is obviously a downside. Since my toolkit generates an interpreter, I...