similar to: [LLVMdev] Running VMKit's AOT Java Compiler

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

Hello, I am trying to build vmkit2 from the repo using OpenJDK 6 (stock install) on Ubuntu 13.04 amd64. When I try to compile vmkit2 I get the core dump below. I am not sure what the issue is, but I was getting the same error when I was also using classpath. My build environment is set up in the following way:

Hi Adam, I don't know which repo you have used? Because only the llvm repo is maintained (not the gforge one), and vmkit2 comes from gforge... By the way, how did you found the gforge repo, it should not be referenced anymore from the web? See you, Gaël Le 21 nov. 2013 17:08, "Adam Pridgen" <Adam.pridgen at rice.edu> a écrit : > Hello, > > I am trying to build

I guess I mispoke, I checked out the source from http://llvm.org/svn/llvm-project/vmkit/trunk. I thought this was vmkit2. I guess I was just referring to vmkit then. On Thu, Nov 21, 2013 at 12:10 PM, Gaël Thomas <gael.thomas00 at gmail.com> wrote: > Hi Adam, > > I don't know which repo you have used? Because only the llvm repo is > maintained (not the gforge one), and

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

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

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

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

Are you running on 64bit (your backtrace addresses suggest you are)? I'm encountering the same error when trying to use VMKit on 64bit, which I believe is an unsupported target. ~Will On Tue, Aug 23, 2011 at 5:17 PM, Frederic Perez Ordeig <fredericp at gmail.com> wrote: > I'm trying to build the SVN version of VMKit and I'm getting this error > while building. > I

I also misunderstood :) So, in this case, the problem is that your version of openjdk is probably not supported. In fact, we only support the version 7u23 of openjdk :) You can find this version here: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html#jdk-7u25-oth-JPR Currently, I'm modifying the internal design of vmkit and I'm not working

Ah yes, thanks, this was one problem, now I hit another: llvm[2]: Building Release+Asserts mmtk-vmkit.jar all Thread 0x110000000 received a SIGSEGV: either the VM code or an external native method is bogus. Aborting... ; 0x5cfeed (0x1100fe410) in _Z14sigsegvHandleriP7siginfoPv ; 0x2b889c232c60 in Unknown method ; 0x561499 (0x1100fe900) in _ZN2j310JavaObject7acquireEPS0_ ; 0x55b464 (0x1100fe920)

Thanks for your help so far Gaël, but I ran into more trouble. I installed the JDK on my system and the messages indicated the JVM version needs to be 1.6. Did you intend to link me to Java 7? LD_LIBRARY_PATH=/usr/lib/jvm/jdk1.7.0_25/jre/lib/amd64/server/:/usr/lib/jvm/jdk1.7.0_25/jre/:/usr/lib/jvm/jdk1.7.0_25/jre/lib/amd64/ Buildfile: /path/to/code/vmkit/mmtk/java/build.xml main: [javac]

Ok, I have exactly the same problem when I compile, I will try to understand where is the problem. Gaël 2013/11/21 Gaël Thomas <gael.thomas00 at gmail.com>: > Arg, you have to use a version strictly before the 7u25 (probably the > 7u21), sorry! > > I hope that it will work, because I also have problem to compile the > trunk version of vmkit (I haven't tested the trunk

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

Arg, you have to use a version strictly before the 7u25 (probably the 7u21), sorry! I hope that it will work, because I also have problem to compile the trunk version of vmkit (I haven't tested the trunk since two months). I'm investigating. Tell me if it works for you with an older version :) See you, Gaël PS: the warning messages are not important 2013/11/21 Adam Pridgen

Hi Michael, On Tue, Dec 8, 2009 at 6:26 PM, Michael Wu <mmwu at princeton.edu> wrote: > 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

Is there a particular revision in the repository that I can checkout and work from? Thanks, -- Adam On Thu, Nov 21, 2013 at 3:46 PM, Gaël Thomas <gael.thomas00 at gmail.com> wrote: > Ok, I have exactly the same problem when I compile, I will try to > understand where is the problem. > > Gaël > > 2013/11/21 Gaël Thomas <gael.thomas00 at gmail.com>: >> Arg, you

Hi, Nicolas Indeed, I did not have ant installed and installing it allowed me to overcome the previous error. However the next one appeared. I have ran make with ENABLE_OPTIMIZED=1 VERBOSE=1 and here is the output (the last part of it) make[2]: Entering directory `/home/svozniuk/llvm/vmkit/mmtk/java' /usr/bin/ant -buildfile /home/svozniuk/llvm/vmkit/mmtk/java/build.xml Buildfile:

Hi Sergii, I think there is a problem in your configure command for VMKit. If you look at what you provide for glibj: --with-gnu-classpath-glibj="/home/svozniuk/llvm/classpath-0.97.2 I don't think it's right. You should change it to: --with-gnu-classpath-glibj="/home/svozniuk/llvm/classpath-0.97.2/lib/glibj.zip Also please make sure that you have created the links for the

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