search for: setmarch

...Or you could just let EngineBuilder call selectTarget for you (which is what the no-argument version of EngineBuilder::create does): llvm::ExecutionEngine * ee = builder. setErrorStr( &errStr ). setEngineKind( llvm::EngineKind::JIT ). setTargetOptions( topts ). setMArch(arch). setMAttrs(mattrs). create(); If those are still failing, it would be interesting to get the data layout string that you are getting from the ExecutionEngine instance and compare it to what you are expecting. Cheers, Lang. On Thu, Apr 19, 2018 at 1:56 AM, edA-qa mort-ora-y...

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

Hello, I'm using Mono with experimental LLVM backend support on PowerPC. I noticed that although LLVM's IR contains SIMD instructions the assembly produced doesn't contain any Altivec instructions and my PowerPC970 machine of course has Altivec support. Isn't there some kind of autodetection? I searched in Target sources but only found out that Altivec is disabled by default. Can

Taking one step back, I'm not clear I'm even setting the triple/DataLayout on the module correctly:     module = new llvm::Module( "test", *llvm_context );     module->setTargetTriple( platform::target->triple ); Is that enough to create an appropriate DataLayout for the module?  I don't see anyway to convert a triple to a DataLayout, so I can't call

This is my first post so not sure I've done everything right. Just started playing with LLVM on Windows 7, VS C++. Was trying to play with the example 4 and got the following error: "LLVM ERROR: Incompatible object format" I was able resolve the problem by following the suggestion found here:http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-December/068395.html This issue seems to

I don't know if I'm setting the triple of my execution engine correctly.  This is leading to an issue where a struct `{i8,i64}` is not getting the same layout as the ABI expects. I setup my engine/module like this:      llvm::SmallVector<std::string,2> mattrs;      llvm::EngineBuilder builder{ unique_ptr<llvm::Module>(module) };      llvm::ExecutionEngine * ee = builder.