similar to: [LLVMdev] Getting oriented : Consuming Java bytecode with LLVM

Hello, I am currently working on the latest version of VMKit (svn trunk). I need to debug VMKit so I tried compiling VMKit in debugging mode (ENABLE_OPTIMIZED=0). To do so I compiled LLVM in debug mode (yes, I really did it...) via: ./configure --enable-debug-runtime --enable-debug-symbols make ENABLE_OPTIMIZED=0 It all went okay for LLVM. Now I tried to compile VMKit in debug mode via:

Hi Nicolas, I am so sorry for the questions. According to you, I built VMKit2 on Ubuntu11.10-desktop-amd64 on Intel(R) Corei5, and the previous problem solved. But another one appeared! With the following configuration: elaheh at elaheh-Lenovo-G470:~/Desktop/vmkit2$ ./configure --with-llvmsrc=/home/elaheh/Desktop/llvm/ --with-llvmobj=/home/elaheh/Desktop/llvm/

Hello Alexandru, No you did nothing wrong. We are using our own data structure to describe annotations in J3. So it is normal that you can not see your Java annotations inside the LLVM bytecode produced. If I remember well, our implementation of annotations do not rely on LLVM annotations. Regards, Harris Bakiras On 06/17/2013 02:19 PM, Alexandru Ionut Diaconescu wrote: > Hello

For anyone who encounters this issue in the future, my issue was the configuration of llvm-gcc. Configure with --with-llvmgccdir=YOUR/PATH doesn't work, instead you are supposed to use --with-llvmgcc=PATH/TO/llvm-gcc and --with-llvmgxx=/PATH/TO/llvm-g++ That will at least get you past my error. Best, Kyle Quoting nicolas geoffray <nicolas.geoffray at gmail.com>: > I am

Hello, I've been able to get J3 working with the single and multimap garbage collectors but have hit several snags with Boehm and MMTk. For MMTk I get here: Buildfile: /cs/student/kyleklein/vmkit/mmtk/java/build.xml main: [mkdir] Created dir: /cs/student/kyleklein/vmkit/mmtk/java/classes [javac] Compiling 373 source files to /cs/student/kyleklein/vmkit/mmtk/java/classes

Hello everyone, I am able to work very well with annotations in C/C++, by using __attribute__((annotate("MYANNOTATION"))) static int a; . Inside the LLVM bytecode I have @llvm.global.annotations and @llvm.var.annotation. However, I was trying to test annotations also in Java, with VMKit. These are the commands that I run: javac -Xlint -g -O Main.java ../Release+Asserts/bin/vmjc Main

On Thu, Jun 7, 2012 at 4:27 PM, Foivos S. Zakkak <foivos at zakkak.net> wrote: > Hi Nicolas, > > I thought MMTk is written in java and it is compiled by javac. > It is compiled by javac to produce Java bytecode. Then vmkit runs the initialization code of MMTk (through the JIT) and generates the binary code through llvm. > retried a clean build with JIT enabled > >

What classpath implementation are you using ? GNUClasspath or OpenJDK ? Harris Bakiras On 06/17/2013 03:57 PM, Alexandru Ionut Diaconescu wrote: > Hello Harris, > > Thank you for your answer. So it is there a way of annotating > variables in Java Code, so I can see them into LLVM bytecode? > > Thank you ! > > > On Mon, Jun 17, 2013 at 3:54 PM, Harris BAKIRAS

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 Nicolas, I found a 32bit Lucid machine (but it'd be great if there was a working 64bit version though). Everything was checked out this morning. I now am able to build vmkit with this configuration: ./configure --with-llvmsrc=/home/zoewolk/RESEARCH/llvm --with-llvmobj=/home/zoewolk/RESEARCH/llvm --with-gnu-classpath-glibj=/home/zoewolk/RESEARCH/classpath-0.97.2/lib

Hi Fovios, Do you have a ./lib/j3/LLVMRuntime/LLVMRuntime.inc file being generated? What does it contain? Nicolas On Thu, Jun 7, 2012 at 5:47 PM, Foivos S. Zakkak <foivos at zakkak.net> wrote: > Still the same. > > Is there any chance that the placement of my directories are causing this? > > Also the exact command that fails is > >

Hi, I wanted to use VMKit project to convert Java Bytecode to LLVM IR bitcode. But I do not know how to start, since I came to know that VMkit is written for llvm -3.3 version, but I want it for latest LLVM version 6.0.1. So, could you please suggest me, whether I have to write it whole project from scratch to meet my requirement of latest llvm version, or can use existing project by building

Still the same. Is there any chance that the placement of my directories are causing this? Also the exact command that fails is /home1/public/zakkak/java/vmkit/Release+Asserts/bin/vmjc -std-compile-opts -load=/home1/public/zakkak/java/vmkit/Release+Asserts/lib/MMTKRuntime.so -load=/home1/public/zakkak/java/vmkit/Release+Asserts/lib/MMTKMagic.so -LowerMagic

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:

Hello Harris, Thank you for your answer. So it is there a way of annotating variables in Java Code, so I can see them into LLVM bytecode? Thank you ! On Mon, Jun 17, 2013 at 3:54 PM, Harris BAKIRAS <h.bakiras at gmail.com> wrote: > Hello Alexandru, > > No you did nothing wrong. > > We are using our own data structure to describe annotations in J3. So it > is normal

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

Thanks Favios for finding the problem! I have applied a patch to Makefile.rules, hopefully it now works without you editing some files. About VMKIT_SRC_ROOT and PROJ_SRC_ROOT, it is fine to have both in the code. I find it clearer to use VMKIT_SRC_ROOT. Nicolas On Sun, Jun 10, 2012 at 10:09 PM, Foivos S. Zakkak <foivos at zakkak.net>wrote: > Hi Nicolas, > > I finally found the

Hi Akshat, Could you give us your configuration? CPU/OS? How did you configure and build llvm and vmkit? Nicolas On Thu, Aug 25, 2011 at 4:12 AM, Akshat Gupta <g.akshat at gmail.com> wrote: > Hi, > I tried building again with the latest llvm. > I am getting another seg fault: > > make[2]: Entering directory `/root/code/vmkit/mmtk/java' > Buildfile:

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

On Fri, Aug 26, 2011 at 1:08 AM, Akshat Gupta <g.akshat at gmail.com> wrote: > Hi, > Here are my build details. > OS: > Linux scop 2.6.38-gentoo-r6 #1 SMP Sat Jul 9 13:07:18 EST 2011 i686 > Intel(R) Core(TM) i5-2415M CPU @ 2.30GHz GenuineIntel GNU/Linux > Machine: VirtualBox (32 bit) > > Configure (VMKit): > ./configure --with-llvmsrc=/root/code/llvm