search for: m_llvmmod

Displaying 5 results from an estimated 5 matches for "m_llvmmod".

2012 May 14
2
[LLVMdev] MCJIT
...perhaps calling setUseMCJIT(true) after having already called create()? Can you step through EngineBuilder::create() and see what's happening there? > > -Jim lli.cpp instantiates the builder, sets options/flags etc and then calls create(). In my driver, I have: > llvm::EngineBuilder(m_LLVMMod).setErrorStr(&engErr).setUseMCJIT(true).create(); which is what you mentioned. I'll step through create() and check whats happening. thanks, ashok
2012 May 14
0
[LLVMdev] MCJIT
...JIT(true) after having already called create()? Can you step through EngineBuilder::create() and see what's happening there? >> >> -Jim > > lli.cpp instantiates the builder, sets options/flags etc and then calls > create(). In my driver, I have: >> llvm::EngineBuilder(m_LLVMMod).setErrorStr(&engErr).setUseMCJIT(true).create(); > > which is what you mentioned. I'll step through create() and check whats > happening. My bad about MCJIT flag not being used (must have the code before I switched to trunk). It *IS* used and the MCJIT constructor is being invok...
2012 May 14
2
[LLVMdev] MCJIT
...eady called create()? Can you step through EngineBuilder::create() and see what's happening there? >>> >>> -Jim >> >> lli.cpp instantiates the builder, sets options/flags etc and then calls >> create(). In my driver, I have: >>> llvm::EngineBuilder(m_LLVMMod).setErrorStr(&engErr).setUseMCJIT(true).create(); >> >> which is what you mentioned. I'll step through create() and check whats >> happening. > > My bad about MCJIT flag not being used (must have the code before I switched to trunk). It *IS* used and the MCJIT cons...
2012 May 14
0
[LLVMdev] MCJIT
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. >>>> >>> >>> Do I need to enable anything at configure, my
2012 May 14
2
[LLVMdev] MCJIT
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