search for: setusemcjit

...vs. the old JIT is done in the EngineBuilder. If you're using lli, you can pass -use-mcjit on the command line. If you're using your own driver, you can use the lli.cpp for a reference. > > -Jim Thats what I was pointed to earlier, and following that I set the flag in EngineBuilder.setUseMCJIT(true). I looked at the code of EngineBuilder, it saves the flag but the flag doesnt seem to be used anywhere. Am I missing something? thanks, ashok

...s done in the EngineBuilder. If you're using lli, you can pass -use-mcjit on the command line. If you're using your own driver, you can use the lli.cpp for a reference. >> >> -Jim > > Thats what I was pointed to earlier, and following that I set the flag in EngineBuilder.setUseMCJIT(true). I looked at the code of EngineBuilder, it saves the flag but the flag doesnt seem to be used anywhere. Am I missing something? Hm. OK, that's odd. It should change which constructor gets called in EngineBuilder::create() (which is in lib/ExecutionEngine/ExecutionEngine.cpp). Are you pe...

...EngineBuilder. If you're using lli, you can pass -use-mcjit on the command line. If you're using your own driver, you can use the lli.cpp for a reference. >>> >>> -Jim >> >> Thats what I was pointed to earlier, and following that I set the flag in EngineBuilder.setUseMCJIT(true). I looked at the code of EngineBuilder, it saves the flag but the flag doesnt seem to be used anywhere. Am I missing something? > > Hm. OK, that's odd. It should change which constructor gets called in EngineBuilder::create() (which is in lib/ExecutionEngine/ExecutionEngine.cpp). A...

On 08/02/13 15:42, David Tweed wrote: > | For ARM, you will need to use the MCJIT ExecutionEngine as the legacy > | one is broken for ARM. (call EngineBuilder::setUseMCJIT()). > > Also remember to include the correct MCJIT headers not the JIT one's: > calling setUseMCJIT() with the old JIT headers are the only ones being > included just constructs an old JIT, it doesn't spit out a helpful warning > like "I can't build an MCJIT JIT for...

Renato Golin wrote: [...] > Try setting armv7a-unknown-linux-gnueabihf and see if it works better. No, that doesn't work either. [...] > JIT was never the forte of ARM and I haven't tried yet, but I doubt > it'll be any Debian misconfiguration. The whole architecture > configuration is a bit odd... Debian's clang packages are totally broken on armhf --- the compiler

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 > > lli.cpp instantiates the builder, sets options/flags etc and then calls > create(). In my driver, I have: >> llvm::EngineBuilder(m_L...

Hi David, For ARM, you will need to use the MCJIT ExecutionEngine as the legacy one is broken for ARM. (call EngineBuilder::setUseMCJIT()). When creating your TargetOptions, setting FloatABIType to FloatABI::Hard should trigger codegen for the correct ABI. Amara

> The newer system is called the MCJIT, and *should* work on ARM. If you look at how lli is implemented (tools/lli/lli.cpp) you should be able to see calls to "setUseMCJIT" which you'll want to duplicate in your code. Side note: this won't work in 2.8 :) In any case, asking for proper ARM codegen in 2.8 is a big challenge. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

...VM 3.1. What could be the reason? I tried to play with TargetOptions without any success… Here is the kind of code we use to allocate the JIT: EngineBuilder builder(fResult->fModule); builder.setOptLevel(CodeGenOpt::Aggressive); builder.setEngineKind(EngineKind::JIT); builder.setUseMCJIT(true); builder.setCodeModel(CodeModel::JITDefault); builder.setMCPU(llvm::sys::getHostCPUName()); TargetOptions targetOptions; targetOptions.NoFramePointerElim = true; targetOptions.LessPreciseFPMADOption = true; targetOptions.UnsafeFPMath = true; targetOptions.NoIn...

...lkund <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 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: >>&g...

...tured argument passing not supported yet! UNREACHABLE executed at MCJIT.cpp:322! I'm sure the first one will be a problem, but the second one prevents me from testing anything. I don't know how to fix the problem. My code works when using the non-MC JIT, and I added to my EngineBuilder: .setUseMCJIT(true) Reading from a tutorial* I also tried finalizing the engine object: ee->finalizeObject() I'd like to get this working since in the release notes for 3.4 it indicates exception handling has been removed from the old JIT. I need exception handling support and would like to get MCJIT w...

With the following call: llvm::ExecutionEngine* engine; llvm::EngineBuilder builder( module ); builder.setEngineKind( llvm::EngineKind::Either ); // it will use JIT if available builder.setUseMCJIT ( true ); engine = builder.create(); These calls are successful in windows. But when I try in Linux (Ubuntu), the create() function fails with the error message: Target does not support MC emission Any ideas why and how to fix it? Thanks. -- Xinglin Zhang -------------- next part -------------...

Greetings, I have a simple C++ EDSL working using the JIT execution engine. When I upgraded to LLVM 3.2 (effortless upgrade, awesome stuff!) I thought I would try taking the MCJIT for a spin after having read that the JIT is considered to be "legacy". So the changes I made to my code were: + #include <llvm/ExecutionEngine/MCJIT.h> - #include <llvm/ExecutionEngine/JIT.h> +

...this fault indicates you're trying to use the legacy one which can just about be relied on not to fail horribly for x86 (usually). The newer system is called the MCJIT, and *should* work on ARM. If you look at how lli is implemented (tools/lli/lli.cpp) you should be able to see calls to "setUseMCJIT" which you'll want to duplicate in your code. Your .ll code looks fine. Cheers. Tim

...t; I tried to play with TargetOptions without any success… > > Here is the kind of code we use to allocate the JIT: > > EngineBuilder builder(fResult->fModule); > builder.setOptLevel(CodeGenOpt::Aggressive); > builder.setEngineKind(EngineKind::JIT); > builder.setUseMCJIT(true); > builder.setCodeModel(CodeModel::JITDefault); > builder.setMCPU(llvm::sys::getHostCPUName()); > > TargetOptions targetOptions; > targetOptions.NoFramePointerElim = true; > targetOptions.LessPreciseFPMADOption = true; > targetOptions.UnsafeFPMath...

...he information to use AVX > (llc -mattr=+avx). > I guess the corresponding code should look like this: > >     llvm::EngineBuilder engineBuilder(module); >     engineBuilder.setErrorStr(&eeError); >     engineBuilder.setEngineKind(llvm::EngineKind::JIT); >     engineBuilder.setUseMCJIT(true); >     engineBuilder.setMCPU("corei7-avx"); >     std::vector<std::string> attrs; >     attrs.push_back("avx"); >     engineBuilder.setMAttrs(attrs); >     llvm::ExecutionEngine *ee = engineBuilder.create(); > > Note that I have just today filed...

...ecuted at MCJIT.cpp:322! > I'm sure the first one will be a problem, but the second one prevents me > from testing anything. I don't know how to fix the problem. > > My code works when using the non-MC JIT, and I added to my > EngineBuilder: > .setUseMCJIT(true) > > Reading from a tutorial* I also tried finalizing the engine object: > ee->finalizeObject() > > I'd like to get this working since in the release notes for 3.4 it > indicates exception handling has been removed from the old JIT. I need &gt...

Hi all, I'm trying to extend the Dalvik VM to load some LLVM assembly from the SD card, JIT it, and execute it. I'm using AOSP 4.0.4, a Galaxy Nexus, and the version of LLVM that comes in the external project of AOSP (LLVM 2.8, I believe?) I have the following LLVM assembly: target datalayout =

...oking llc, you need to pass the information to use AVX (llc -mattr=+avx). I guess the corresponding code should look like this: llvm::EngineBuilder engineBuilder(module); engineBuilder.setErrorStr(&eeError); engineBuilder.setEngineKind(llvm::EngineKind::JIT); engineBuilder.setUseMCJIT(true); engineBuilder.setMCPU("corei7-avx"); std::vector<std::string> attrs; attrs.push_back("avx"); engineBuilder.setMAttrs(attrs); llvm::ExecutionEngine *ee = engineBuilder.create(); Note that I have just today filed a bug report also related to...

...gt; UNREACHABLE executed at MCJIT.cpp:322! > I'm sure the first one will be a problem, but the second one prevents me > from testing anything. I don't know how to fix the problem. > > My code works when using the non-MC JIT, and I added to my EngineBuilder: > .setUseMCJIT(true) > > Reading from a tutorial* I also tried finalizing the engine object: > ee->finalizeObject() > > I'd like to get this working since in the release notes for 3.4 it > indicates exception handling has been removed from the old JIT. I need > exception handli...