similar to: [LLVMdev] Is anyone working on a Windows VmKit port?

Hi -- I'm still very much a newbie with llvm, but am looking (hopefully) to use it to compile into native intel code a set of source that is a combination of byte codes for my own custom vm and intel code that has been coded in assembly language directly. In an earlier exchange, I already discovered that llvm does not do any optimizations on intel assembly language code. This would be an

Hi Folks -- Let me go ahead and pose a question similar to the one Joachim poses below. I too am trying to evaluate whether LLVM will be of use to me in building a compiler and garbage collection mechanism for a byte code vm that I have built. Although there are multiple types of code that can be created with this system, all of them eventually translate to execution of one or more of these

Michael Clagett <mclagett at hotmail.com> writes: > There's about 32 core op codes that constitute the basic instruction > set and I can envision mapping each of these to some sequence of LLVM > IR. There's also a whole lot more "extended opcodes" that are > executed by the same core instruction execution loop but which are > coded using the built-in Intel

If you x86 assembly is sufficiently simple, I don't see any reason why you couldn't programmatically raise it back up to LLVM IR. People have tried this in the past (qemu, I think? I can't remember), and it usually results in some considerable slowdowns. I'd imagine that if your asm is sufficiently restricted, such as not needing to worry about arithmetic flags, the x87 FPU

Hi Everyone -- I'm planning on using LLVM to add some optimizing compiling capability to a Byte-Code driven virtual machine that is part of my foundation platform for a series of tool products I am building. I'm still pretty new to this whole arena and am in particular curious about one important aspect: It strikes me that the more optimizations applied to code (whether at the source

Sorry for the noise, but this is the message I meant to send to the list rather than replying to David directly. Unfortunately, I just sent his message to me before. From: mclagett at hotmail.com To: greened at obbligato.org Subject: RE: [LLVMdev] LLVM IR is a compiler IR Date: Thu, 6 Oct 2011 19:44:11 +0000 Thanks for your prompt reply. My answers are below at the end of your message.

On Tue, Aug 16, 2011 at 1:45 PM, Nicolas Geoffray <nicolas.geoffray at gmail.com> wrote: >> Supporting OpenJDK is very interesting indeed, as full 1.6 support is >> important to us.  How intense of a project would undertaking this be? >> And is this something you could semi-mentor on if I were to undertake >> it? :). > > Yes, no problem. I'd be happy to help

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 -- I'm wondering if some of you old hands might offer me some guidance. I've been working for some time with a virtual machine platform that is based loosely on the instruction set of a Forth hardware processor that Charles Moore designed sometime back. He used what he called a "MISC" or "Minimal Instruction Set Computer" and the original instruction set I was

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 all, I'm interested in using VMKit rather extensively in a project of mine. I was hoping to get feedback on a few vmkit-related questions from those more familiar: --Is there a 'best' version to use? I'd be inclined to use the 2.9 release since it's a stationary target, but curious if I should try to follow ToT.  Is there a recommended best practice? --What features of

Hi all, I'm working on implementing exceptions in Pyston, and I was hoping to get some guidance from the list. I think I've learned enough about C++-style DWARF exceptions to convince myself I have a workable approach, but then I found this VMKit paper (2010) which says The exception manager: To manage exceptions, J3 reserves a > word for the pending exception in the local storage of

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,

Hello, I'm trying to compile vmkit on a x86_64 linux box with gcc-4.1.2, but I'm running into troubles because of various problems with casts between pointers and integers. Is there anybody who succeeded in this task? Az I see, some of the problems can be fixed with an appropriate typedef/macro declaration, but in VMCore/JavaObject.cpp some lowlevel bitmanipulation is used, to mark

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 Nicolas, No, I built llvm-gcc myself by checking it out via svn, using these instructions: http://llvm.org/docs/GCCFEBuildInstrs.html thanks -Z > Hi Zoe > (Please, try to reply to the same thread) > I think you may have an old version of llvm-gcc. Did you compile > llvm-gcc yourself? The provided llvm-gcc binary for llvm 2.7 is > too old for vmkit. > > Nicolas >

Hi Zsombor, Thanks for the patch! Unfortunately I can't apply it because the llvm API has moved from BinaryOperator::create to BinaryOperator::Create. Are you using svn head? Now on the x86_64 part. There has been very little work on porting vmkit on x86_64. If you're having compilation problems, I suppose it's in the garbage collector directory (GCMmap2). If you could make the

On Tue, Jul 20, 2010 at 6:36 PM, Joshua Warner <joshuawarner32 at gmail.com>wrote: > Sure, that's one major strength of LLVM: we could decide on a runtime >> function (CallVirtualMethod) that will get lowered depending on the >> underlying VM. I don't see any difficulties in accomplishing this. >> > > Is it common practice to emit function calls that are

On Tue, Jul 20, 2010 at 9:52 AM, nicolas geoffray < nicolas.geoffray at gmail.com> wrote: > On Tue, Jul 20, 2010 at 5:35 PM, Joshua Warner <joshuawarner32 at gmail.com>wrote: > >> Hi Nicolas, >> >> I plan on using the Avian GC (which is a precise, generational >> collector). >> > > OK - Great! > > >> Eventually, I'd like to

Hello, Edwin > Probably there are more 64-bit issues to solve. Unfortunately I don't > have time to look into this deeper now. At least these "4" looks pretty suspicious: - (void *)gcset((gc **)((unsigned int)this + nbb + 4 - sizeof(void *)), + (void *)gcset((gc **)((size_t)this + nbb + 4 - sizeof(void *)), (Object*)m); -- With best