similar to: [LLVMdev] Unable to build vmkit

Oups, sorry for the mistake, llcj (not llc:)) is not more maintained! Gaël Le 10 sept. 2014 00:27, "Gaël Thomas" <gael.thomas00 at gmail.com> a écrit : > Hi Brian, > > So, I confirm, llc is not more maintained. And using vmjc is probably > the good starting point to translate Java bytecode into llvm bitcode. > > However, I think that your hack (changing the way

Hello again Gaël, (et al) More on rekindling work on VMKit! Thank you for your interactions thus far on- and off-list. As you suggested in your VMKit-retirement email (to which I'm attempting to respond), I'm interested in producing a Java-to-LLVM compiler out of VMKit. I'd like to take you up on your offer to help understand the architecture. If I can get the a Java-to-LLVM

Hi everyone, I wanted to have a closer look at VMKit because I would like to play with modifications to a JVM. I followed the instructions at http://vmkit.llvm.org/get_started.html step by step and got everything compiled without much difficulty on my MacBook (running MacOS X 10.6.3). The only modification that I needed to make was to add -L/usr/X11R6/lib to LDFLAGS for compiling the GNU

Hi Does anybody use *StartJnjvmWithJIT* from jvjvm.cpp in VMKit? Becuase , I am looking to use without JIT when we are running the Java byte code. My concern is StartJnjvmWithJIT getting three argument *int argc, char** argv, char* mainClass* - why we need to pass *argv and mainclass* arguments here? please help me on this. Regards Sri. -------------- next part -------------- An

Hi, I just did a reconfigure and rebuild with the latest svn for vmkit code. The code still seg faults but the stack trace seems to have changed. llvm[2]: Building Debug+Asserts mmtk-vmkit.jar all vmjc: JavaRuntimeJIT.cpp:172: uint32 j3VirtualTableLookup(j3::Class*, uint32, uint32*, j3::JavaObject*): Assertion `dmeth->classDef->isInitializing() && "Class not ready in a virtual

Thanks Nicolas, I do have --with-gnu-classpath-libs and --with-gnu-classpath-glibj pointing to the right thing, but I have gnu class path 0.98 instead of 0.97 and its the non X version. So I do not have the libgtkpeer.so. Maybe that is the reason why it is crashing. Unfortunately, I am not able to compile GNU class path with gtk+ peer right now. Will give it a try on the mac. Thanks, Akshat

This error usually shows up when vmkit cannot find the classpath libs and jar. Make sure --with-gnu-classpath-libs points to the directory of .so files are, and that --with-gnu-classpath-glibj points to glibj.zip. Nicolas On Sat, Aug 27, 2011 at 5:13 AM, Akshat Gupta <g.akshat at gmail.com> wrote: > Hi, > I just did a reconfigure and rebuild with the latest svn for vmkit code. >

Hi Akshat, Please use version 0.97.2. vmkit does not support 0.98. Also, it should be fine to not compile gtk+ peer. Nicolas On Mon, Aug 29, 2011 at 8:58 PM, Akshat Gupta <g.akshat at gmail.com> wrote: > Thanks Nicolas, > I do have --with-gnu-classpath-libs and --with-gnu-classpath-glibj > pointing to the right thing, but I have gnu class path 0.98 instead of 0.97 > and its

I just noticed there was some .h move around in llvm and fixed the includes in vmkit. Maybe you were just removing the failing includes? In any case, I have updated vmkit for llvm trunk. Let me know if updating helps. Nicolas On Fri, Aug 26, 2011 at 12:00 PM, Akshat Gupta <g.akshat at gmail.com> wrote: > Yep, I am compiling with llvm-gcc. Also I removed the LD flag on the >

Yep, I am compiling with llvm-gcc. Also I removed the LD flag on the configure, it still gives the same segafault. Thanks, Akshat On Fri, Aug 26, 2011 at 4:21 AM, Nicolas Geoffray < nicolas.geoffray at gmail.com> wrote: > On Fri, Aug 26, 2011 at 1:08 AM, Akshat Gupta <g.akshat at gmail.com> wrote: > >> Hi, >> >> Here are my build details. >> OS: >>

Hi, I'm new to VMKit and I'm trying to use its AOT Java compiler but I'm immediately getting an error message which I don't understand. Everything was compiler as suggested in the Getting Started tutorial, using GNU Classpath. I try to run: llcj ../../tools/trainer/Release+Asserts/HelloWorld.class and get the following output: Can not materiale a function in AOT mode.0

Hi, What do I need to link with vmjc created .bc files to actually run the .bc file? I tried running with lli but only got: LLVM ERROR: Program used external function 'StartJnjvmWithoutJIT' which could not be resolved! Thanks, Michael

Hi Nicolas, it looks like there are missing things $ more lib/j3/LLVMRuntime/LLVMRuntime.inc // Generated by llvm2cpp - DO NOT MODIFY! Module* makeLLVMModuleContents(Module *mod) { mod->setModuleIdentifier("<stdin>"); // Type Definitions // Function Declarations // Global Variable Declarations // Constant Definitions // Global Variable Definitions // Function

Hi Michael, Currently, you can run vmjc created .bc files by statically linking them with all the .o needed files. For that, you can use the llcj tool, which works more or less like GCC's gcj tool. Note that you also need to create the libvmjc.so file, which contains the standard library in native form. Do a make in the tools/vmjc/libvmjc directory. Once this is done, update the

Hi, Thanks a lot for the help! I am getting some errors though: I am on a 32 bit chroot on a x86_64 system. Thus llc guesses the wrong architecture from the module bitcode and spits out x86_64 assembly. I fixed this by adding "-march=x86" to the llc options in llcj. gcc doesn't know what -lgc is. I'm guessing it is the garbage collection library. How can I get it or

Hi Nicolas, I finally found the root of the problem. Build was unable to locate llvm-build because it was looking for it in path/to/vmkit_src/utils/llvm-build while it was located in path/to/llvm_src/utils/llvm-build Actually llvm-build's path is defined by the path/to/llvm_src/Makefile.rules and looks like this LLVMBuildTool := $(PROJ_SRC_ROOT)/utils/llvm-build/llvm-build however in

Hi, I am trying to evaluate how complex would be to modify KLEE ( http://klee.llvm.org/ ) so that it can run LLVM bitcode compiled from Java code obtained with vmjc (from the VMKIT project). Your feedback will be very appreciated. I am familiar with KLEE but I would like to know more about VMKIT, so please point me to the right docs/source code if appropriate. After a quick look over

Hi, I've managed to compile it the class down to a native executable. However, the executable runs for a while then spits out: terminate called without an active exception Aborted and dies. The program never gets to the normal output. Here is a stack trace from gdb: #0 0xf3f6baa6 in raise () from /lib/libc.so.6 #1 0xf3f6d3a8 in abort () from /lib/libc.so.6 #2 0xf41918f8 in

Hmm, disregard my previous comment (while you might still have issues with 64bit, that's not what's primarily causing your issue)--your particular error is when you don't point vmkit to the classpath libraries properly. Set it with the configure option --with-gnu-classpath-glibj=/path/to/classpath-0.97.2/lib/glibj.zip Good luck! ~Will On Tue, Aug 23, 2011 at 5:49 PM, Will Dietz

I'm trying to build the SVN version of VMKit and I'm getting this error while building. I have llvm and clang built from SVN too. Any help? llvm[2]: Building Release+Asserts mmtk-vmkit.jar all vmjc: JavaClass.cpp:442: j3::JavaObject *j3::Class::doNew(j3::Jnjvm *): Assertion `this && "No class when allocating."' failed. 0 vmjc 0x0000000000e9c44f 1 vmjc