similar to: [LLVMdev] VMKit - J3's startup time

Hi Chanwit, What problems did you have for compiling the latest revision? Could you give me a log? Thanks, Nicolas On Thu, Jul 8, 2010 at 10:05 PM, Chanwit Kaewkasi <chanwit at gmail.com> wrote: > Thank you, Nicolas. > But I still have no luck compiling the latest revision. However, > vmkit-0.27 is compiled and running fine on my machine. > > Thanks, > > Chanwit >

Hi Nicolas, Here it is. Please review. Thanks, Chanwit On Tue, Jul 13, 2010 at 23:52, nicolas geoffray <nicolas.geoffray at gmail.com> wrote: > Hi Chanwit, > Thanks for the patch! Could you change it to detect the ant executable > instead of the ANT_HOME variable? > Nicolas > > On Tue, Jul 13, 2010 at 5:34 AM, Chanwit Kaewkasi <chanwit at gmail.com> wrote:

Hi, Please find in the attachment a patch for configure.ac to detect ANT_HOME, when running configure --with-gc=mmtk. Cheers, Chanwit -------------- next part -------------- A non-text attachment was scrubbed... Name: ant_home_ac.patch Type: text/x-patch Size: 696 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100713/561e7840/attachment.bin>

Hi Chanwit, Thanks for the patch! Could you change it to detect the ant executable instead of the ANT_HOME variable? Nicolas On Tue, Jul 13, 2010 at 5:34 AM, Chanwit Kaewkasi <chanwit at gmail.com> wrote: > Hi, > > Please find in the attachment a patch for configure.ac to detect > ANT_HOME, when running configure --with-gc=mmtk. > > Cheers, > > Chanwit > >

Latest version of vmkit should now build fine with latest llvm. Nicolas On Wed, Jul 7, 2010 at 11:02 AM, nicolas geoffray < nicolas.geoffray at gmail.com> wrote: > The one that I have currently that works with vmkit is 107120. > > > On Wed, Jul 7, 2010 at 10:58 AM, Chanwit Kaewkasi <chanwit at gmail.com>wrote: > >> Hello Nicolas, >> >> Thank you for

Thank you, Nicolas. But I still have no luck compiling the latest revision. However, vmkit-0.27 is compiled and running fine on my machine. Thanks, Chanwit On Thu, Jul 8, 2010 at 05:18, nicolas geoffray <nicolas.geoffray at gmail.com> wrote: > Latest version of vmkit should now build fine with latest llvm. > Nicolas > > On Wed, Jul 7, 2010 at 11:02 AM, nicolas geoffray >

Hello Nicolas, Thank you for quick reply. Is LLVM revision 107641 a good one to build with latest VMKIT? Thanks, Chanwit On Thu, Jul 8, 2010 at 00:06, nicolas geoffray <nicolas.geoffray at gmail.com> wrote: > Hi all, > Yes, there was a change in the LLVM CallInst API, and I haven't updated > vmkit yet. It should be fixed real soon. > Cheers, > Nicolas > > On Wed,

The one that I have currently that works with vmkit is 107120. On Wed, Jul 7, 2010 at 10:58 AM, Chanwit Kaewkasi <chanwit at gmail.com> wrote: > Hello Nicolas, > > Thank you for quick reply. > Is LLVM revision 107641 a good one to build with latest VMKIT? > > Thanks, > > Chanwit > > On Thu, Jul 8, 2010 at 00:06, nicolas geoffray > <nicolas.geoffray at

Hi, I replaced the MMTk code with a C-version MMTk code (I have been working on such AOT compiler for a while). The compiler should deal with most of the MMTk code base correctly - at least I get marksweep running with a tiny client). So I am trying to put the C version MMTk back with VmKit. I tried not to change much existing code except where necessary, such as name mangling and MMTkObject

Hi Yi, The precompiler is in charge of translating the most common classes of the Java runtime library to llvm code (typically, java.lang.Object), in order to natively compile these classes and decrease the bootstrap time. So, if you have a segmentation fault at this stage, it means that you have broken something in the interface between MMTk and VMKit. If it can helps you: * during a first

Hi all, Yes, there was a change in the LLVM CallInst API, and I haven't updated vmkit yet. It should be fixed real soon. Cheers, Nicolas On Wed, Jul 7, 2010 at 9:50 AM, chanwit <chanwit at gmail.com> wrote: > > Hi, > > Just to comfirm that I have just clean built the current LLVM and VMKIT > revisions and it failed too. > The problem seems to be the same one (about

Hi, Just to comfirm that I have just clean built the current LLVM and VMKIT revisions and it failed too. The problem seems to be the same one (about escape analysis in LLVM). My configuration is Ubuntu 10.04 and GCC 4.4.3 on x86. Cheers, Chanwit Konrad Hinsen-2 wrote: > > On 6 Jul 2010, at 22:25, Zoe Wolk wrote: > >> If anyone is able to build vmkit and get it to run without

Hi Minas, I tried recompiling Classpath with -fno-omit-frame-pointer, and now, instead of printing an error message, j3 just segfaults in "j3::JnjvmClassLoader::loadClassFromAsciiz(char const*, bool, bool) ()" I ran llcj under strace and found that it is not even opening the input or output files, but is otherwise running normally. Updating to the latest SVN version (revision 108831)

I followed instructions in this page to setup my environment: http://vmkit.llvm.org/get_started.html My llvm, llvm-gcc, and vmkit are not SVN version. All of them are downloaded from this page: http://llvm.org/releases/download.html#2.7 GNU classpath is downloaded from: ftp://ftp.gnu.org/gnu/classpath/classpath-0.97.2.tar.gz PNet & PNetlib are not used because I just want the JVM. I

Hi Akshat, Did you compile LLVM before compiling VMKit? libLLVMLinker.so is a shared library from LLVM. Cheers, Nicolas On Thu, Aug 18, 2011 at 3:42 AM, Akshat Gupta <g.akshat at gmail.com> wrote: > Hi, > I was just curious if VMKit development is still going on. > > Also while building VMKit I am getting error at link stage: > > make[1]: Entering directory

Hi, I was just curious if VMKit development is still going on. Also while building VMKit I am getting error at link stage: make[1]: Entering directory `/code/vmkit/tools/vmjc' llvm[1]: Linking Debug+Asserts executable vmjc /usr/lib/gcc/i686-pc-linux-gnu/4.4.5/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lLLVMLinker collect2: ld returned 1 exit status I have installed but I am not able

Hi Akshat, > Going ahead, the llvm-ld seems to segfault (build on Linux with llvm-ld v3.0svn > build): try updating to latest LLVM from svn - this was fixed a day or two ago. Ciao, Duncan. > > make[2]: Entering directory `/root/code/vmkit/mmtk/mmtk-j3' > llvm[2]: Building Debug+Asserts Bytecode Module MMTKRuntime.bc > 0 llvm-ld 0x0884c66e > 1 llvm-ld 0x0884c3fb

Hi, Going ahead, the llvm-ld seems to segfault (build on Linux with llvm-ld v3.0svn build): make[2]: Entering directory `/root/code/vmkit/mmtk/mmtk-j3' llvm[2]: Building Debug+Asserts Bytecode Module MMTKRuntime.bc 0 llvm-ld 0x0884c66e 1 llvm-ld 0x0884c3fb 2 0xb7891400 __kernel_sigreturn + 0 3 llvm-ld 0x083be9e9 llvm::isa_impl<llvm::Constant,

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:

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 >