similar to: [LLVMdev] JIT support for inline asm on Linux

On 5/7/2012 12:21 AM, Bendersky, Eli wrote: <snip> > > MCJIT is functional in trunk (and the 3.1 branch). While it doesn't include all the features of the old JIT quite yet, it's complete enough to pass all of JIT's execution tests on Linux and Mac OS X (no Windows yet). As for directions on how to enable it, follow the path of the "use-mcjit" flag passed to lli

> Hi, > I'm using LLVM/clang from release 3.0. I have a program (C++) that will load > a library in the form of LLVM bit code using the JIT. However, I see JIT errors > when loading the bit code: > > "LLVM ERROR: JIT does not support inline asm" > > I read that MC JIT intends to fix this. I'm trying to build LLVM from the > lastest trunk. Is

On 5/7/2012 10:17 PM, Bendersky, Eli wrote: <snip> >>> $lli -entry-function="ISimEngine_GetVersion" -use-mcjit libengine.bc >>> LLVM ERROR: Inline asm not supported by this streamer because we don't >>> have an asm parser for this target >> >> I also tried other variations of the call with the same result: >>> $lli

> On 5/7/2012 12:21 AM, Bendersky, Eli wrote: > <snip> > > > > MCJIT is functional in trunk (and the 3.1 branch). While it doesn't include all > the features of the old JIT quite yet, it's complete enough to pass all of JIT's > execution tests on Linux and Mac OS X (no Windows yet). As for directions > on how to enable it, follow the path of the

Resending, any pointers are much appreciated. On 5/7/2012 11:16 PM, Ashok Nalkund wrote: > > > On 5/7/2012 10:17 PM, Bendersky, Eli wrote: > <snip> >>>> $lli -entry-function="ISimEngine_GetVersion" -use-mcjit libengine.bc >>>> LLVM ERROR: Inline asm not supported by this streamer because we don't >>>> have an asm parser for this

Hi, LLVM/Clang version: 3.2svn (r156975). I have a bitcode file that I'm trying to load/execute using lli as below but it reports an error about unresolved symbol: > LLVM ERROR: Program used external function '_ZNKSt3__16locale9use_facetERNS0_2idE' which could not be resolved! > lli: /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/lib/Support/ThreadLocal.cpp:54:

Resending, any pointers? I demangled the symbol and it turns out to be: std::__1::locale::use_facet(std::__1::locale::id&) const tia, ashok On 5/19/2012 9:41 PM, Ashok Nalkund wrote: > Hi, > LLVM/Clang version: 3.2svn (r156975). I have a bitcode file that I'm > trying to load/execute using lli as below but it reports an error about > unresolved symbol: >> LLVM

Hi, I'm finally moving cling to MCJIT - and MCJIT is wonderful! So far I only ran into this issue: $ cat linkonceodr.cxx extern "C" int printf(const char*,...); template <class T> struct StaticStuff { static T s_data; }; template <class T> T StaticStuff<T>::s_data = 42; int compareAddr(int* mcjit); #ifdef BUILD_SHARED int compareAddr(int* mcjit) { if (mcjit

Following along from lli code, if you add a call to InitializeNativeTargetAsmPrinter() during setup, it gets a bit farther and crashes rather than issuing that error. (Rebuilding with debugging symbols now to dig into it further…) -matt Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000 0x000000010000349e in

Hi Keno, The part that scares me a bit is > and then adjust the other methods to not > bail out two quickly when encountering a weak symbol. I would very much appreciate if you could implement this; I don't have enough knowledge of the MCJIT nor llvm CodeGen internals... I will happily try it out and provide you with feedback, though! :-) Thank you *so* much for your fast reaction!

On 5/14/2012 10:28 AM, Jim Grosbach wrote: > > On May 14, 2012, at 10:21 AM, Ashok Nalkund<ashoknn at qualcomm.com> wrote: > >> On 5/14/2012 9:51 AM, Jim Grosbach wrote: >>> >>>>> >>>>> If you're hitting that code, you're running the old JIT (which does indeed not support inline assembly), not the MCJIT. >>>>>

Hi Ralf, FYI, old JIT doesn't support AVX at all, no encoding info, etc... The only way to use AVX+JIT is using MCJIT, which contains the correct encoding, but unfortunately the framework isn't good yet as the old one is. On Thu, Aug 25, 2011 at 10:12 AM, Ralf Karrenberg <Chareos at gmx.de> wrote: > Hi Matt, > > I am unsure about MCJIT, but I guess the problem is the same.

I'm trying to wire up some code to use the MC-based JIT; my understanding is that it should be able to JIT AVX code (and that the regular JIT cannot). However, I'm getting the error "Target does not support MC emission!" when I call EngineBuilder::create(). I assume that I'm just not doing something necessary for initialization, but I'm not sure what it would be--I am

On 5/14/2012 10:40 AM, Ashok Nalkund wrote: >> >> Hm. OK, that's odd. It should change which constructor gets called in EngineBuilder::create() (which is in lib/ExecutionEngine/ExecutionEngine.cpp). Are you perhaps calling setUseMCJIT(true) after having already called create()? Can you step through EngineBuilder::create() and see what's happening there? >> >> -Jim

Hi, I am first year PhD student at Stony Brook University. For one of my projects I am trying to JIT compile and run a C program containing inline assembly using MCJIT but I am not able to. I have cloned and build LLVM-3.1. Below are more details. Arch : x86 OS : Linux ubuntu 2.6.35-22-generic Sample program : test_inline_asm.c ------------------- #include <stdio.h> int main(){ int

On May 14, 2012, at 11:12 AM, Ashok Nalkund <ashoknn at qualcomm.com> wrote: > On 5/14/2012 10:40 AM, Ashok Nalkund wrote: >>> >>> Hm. OK, that's odd. It should change which constructor gets called in EngineBuilder::create() (which is in lib/ExecutionEngine/ExecutionEngine.cpp). Are you perhaps calling setUseMCJIT(true) after having already called create()? Can

Hi, Using the trunk of svn. I'm trying to get inline-asm working on X86. So I added call to: > InitializeNativeTargetAsmParser() during initialization. However, this causes a linking error: > llvm[2]: Linking Debug+Asserts executable lli > /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/lli/Debug+Asserts/lli.o: In function

Hi Jim, Thanks for the reply. I was able to figure out the problem in 'lli'. InitializeNativeTargetAsmParser() was missing in lli. I should have replied back saying that the problem was resolved. Hope I didn't waste your time. Regards, Amit ________________________________ From: Jim Grosbach [grosbach at apple.com] Sent: Monday, November 05, 2012 2:07 PM To: Amit Arya Cc: LLVM

Hi Amit, You're not doing anything wrong. This is an error in 'lli' not properly initializing the native target libraries. Fixed in SVN trunk r167392. -Jim On Nov 4, 2012, at 4:09 PM, Amit Arya <aarya at cs.stonybrook.edu> wrote: > Hi, > > I am first year PhD student at Stony Brook University. For one of my projects I am trying to JIT compile and run a C program

On 5/14/2012 9:51 AM, Jim Grosbach wrote: > >>> >>> If you're hitting that code, you're running the old JIT (which does indeed not support inline assembly), not the MCJIT. >>> >> >> Do I need to enable anything at configure, my configure looks like this: >>> ../llvm/configure --enable-libffi --enable-targets=host-only