[LLVMdev] Running LLVM JIT on qemu-system-arm

Toan Mai iammxt at gmail.com
Mon Apr 30 05:17:23 PDT 2012


Hi James,

Thanks for your information.
Could you suggest any other framework that I could use for making a custom
JIT for ARM?
I am doing research on JIT compilation for a heterogeneous processor system.

Best,
Toan Mai

On Mon, Apr 30, 2012 at 3:55 PM, James Molloy <james.molloy at arm.com> wrote:

> Hi Toan,
>
> The JIT for ARM (non-darwin) is completely broken and you should not expect
> it to work in its current state.
>
> Cheers,
>
> James
>
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On
> Behalf Of Toan X. Mai
> Sent: 29 April 2012 07:37
> To: llvmdev at cs.uiuc.edu
> Subject: [LLVMdev] Running LLVM JIT on qemu-system-arm
>
>
> Hi all,
>
> I'm struggling to get lli work on qemu-system-arm. I already boot the
> system
> with a debian squeeze rootfs which contains a statically cross-compiled lli
> for armel. When I run ./lli hello.bc, I got the following error msg:
>
> ./lli: error creating EE: /lib/: cannot read file data: Is a directory
>
> afaik, this error is related to lli using dlopen() with a NULL path to
> resolve symbols for the main program (lli program) itself. This happens
> when
> lli initially tries to create an ExecutionEngine ("EE = builder.create();"
> in lli.cpp), which leads to "if
> (sys::DynamicLibrary::LoadLibraryPermanently(0, ErrorStr)" in
> ExecutionEngine.cpp.
>
> Could anyone tell me how to resolve this?
>
> Thanks in advance!
> Toan Mai.
> --
> View this message in context:
>
> http://old.nabble.com/Running-LLVM-JIT-on-qemu-system-arm-tp33763272p3376327
> 2.html
> Sent from the LLVM - Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120430/a099a6b6/attachment.html>


More information about the llvm-dev mailing list