Re: [Neko] LLVM backend: "Hello world" in haXe works

[Philipp Klose]

It gives me:
Version: 2.6-0ubuntu1

Philipp

Vadim Atlygin wrote:

Hi Phillip,

can you check what version of llvm-dev you have installed on your system? You can do it by running 'aptitude show llvm-dev | grep Version' in the command line. But I run Ubuntu 9.10 myself and it is really strange that you experiencing problems in the similar setup.

Best regards.
Vadim.

On Thu, Jun 3, 2010 at 12:00 AM, Philipp Klose <m...@thehippo.de <mailto:m...@thehippo.de>> wrote:

    I am *really* interested in you project an I am following the
    github project. Currently and during the last week I am not able
    to compile out of the box on my Ubuntu 9.10.
    My build process crashes with the following error:

    hi...@hippo:~/neko_llvm_jit$ rake
    (in /home/hippo/neko_llvm_jit)
    make libneko neko std
    cc -Wall -fPIC -g -fomit-frame-pointer -I vm -D_GNU_SOURCE
    -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS
    -DX86TargetMachineModule=1 -DIA64TargetMachineModule=1 -pthread -o
    vm/llvm/jit.o -c vm/llvm/jit.cpp
    vm/llvm/jit.cpp: In function ‘void llvm_cpp_jit(neko_vm*,
    neko_module*)’:
    vm/llvm/jit.cpp:42: error: ‘GuaranteedTailCallOpt’ is not a member
    of ‘llvm’
    vm/llvm/jit.cpp:43: error: ‘JITEmitDebugInfo’ is not a member of
    ‘llvm’
    make: *** [vm/llvm/jit.o] Fehler 1
    rake aborted!
    Command failed with status (2): [make libneko neko std...]
    /home/hippo/neko_llvm_jit/Rakefile:13
    (See full trace by running task with --trace)


    Philipp



    Asger Ottar Alstrup wrote:

        Hi,

        Today, Vadim finished implementing all of the opcodes, and now
        "Hello world" in haXe works. This includes jitting and running
        all of the haXe neko runtime before finally printing "Hello
        world". Jitting the runtime takes about a second, but it is a
        significant milestone: now it works.

        >From now on, the next steps are to try with bigger haXe
        programs, and fix any remaining bugs. After this, work can
        start to profile and optimize this stuff. Right now, about 19
        of the opcodes are C callbacks, and thus not subject to LLVM's
        optimizations. Depending on what the profiling and
        optimization work turns out, some of those opcodes can be
        rewritten to LLVM opcodes to expose more stuff to optimizations.

        The link to the code is here:

        http://github.com/vava/neko_llvm_jit

        Go check it out. If you have a Linux box, it is really easy to
        compile the code and try it out.

        Regards,
        Asger

-- Neko : One VM to run them all

    (http://nekovm.org)

-- 
Neko : One VM to run them all
(http://nekovm.org)