similar to: [LLVMdev] [PATCH] 8975 - llc should warn about invalid target triple

Hi César, > I changed Module::setTargetTriple to return true/false when an > invalid/valid triple is passed as parameter. target triples with unknown vendor and other fields occur all the time. That's fine as long as you don't need those fields. What I am saying is that a boolean value "valid" or "not valid" isn't very useful in my opinion. Ciao, Duncan.

Hi edaqa, You might need to set your TargetOptions before calling selectTarget. E.g. builder.setTargetOptions(Opts).selectTarget(...); 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 ).

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

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.    

I am currently setting up my Module with module->setTargetTriple(llvm::sys::getProcessTriple() #ifdef _WIN32 + "-elf" #endif ); And my ExecutionEngine with llvm::EngineBuilder(std::move(module)) .setErrorStr(&err) .setMCPU(llvm::sys::getHostCPUName())

This is from https://stackoverflow.com/questions/48360685/no-targets-in-targetregistry I have the following code, which should get the default llvm::Target. auto const targetTriple = llvm::sys::getDefaultTargetTriple(); llvm_module.setTargetTriple(targetTriple); std::string error; auto const * target = llvm::TargetRegistry::lookupTarget(targetTriple, error); if (target ==

I duplicated an instruction in llvm and changed its opcode by following the guide at https://llvm.org/docs/ExtendingLLVM.html (Adding a new instruction) and then fixed the dependencies that caused an error when building. Now the modified llvm builds but throws but now throws the error: llc: error: llc: check.ll:12:3: error: instruction expected to be numbered '%5' %4 = alloca i32, align

I'm using the Debian LLVM package to try and do JIT on a Linux armhf device. Unfortunately it seems to be generating armel code rather than armhf code, and since the ABIs don't match nothing works. I've tried overriding the triple to arm-unknown-linux-gnueabihf and arm-linux-gnueabihf (via module->setTargetTriple), and while the triples are accepted, the actual generated code

Hi Tim, Thank you for that. I was just trying to replicate the branch instruction under a new opcode, so I don’t think that returns a value. Plus the code I was testing out didn’t have a br or my newly added instruction but it still threw that error at me. Here’s the IR code I tested: ; ModuleID = ‘cc.c’ source_filename = “cc.c” target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128”

Hi, I am trying to implement a scenario similar to running ExceptionDemo.cpp with parameter -1 (where the JITed code calls the C++ function which throws an exception) Different from the given example I am using IRParser instead of IRBuilder. I can successfully catch the exception in Linux but the program crashes in Mac and Windows. The code is similar to as follows: ### The test.cpp :

These warnings started appearing recently when building LLVM: llvm[2]: Compiling LLParser.cpp for Release build /Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp: In member function ‘bool llvm::LLParser::ParseBr(llvm::Instruction*&, llvm::LLParser::PerFunctionState&)’: /Volumes/Data/Users/kremenek/llvm/lib/AsmParser/LLParser.cpp:3195: warning: ‘Op1’ may be used uninitialized in

Cordial saludo para cada uno. De manera amable les pido ayuda para acceder al código R usado para el algoritmo de la función qnorm. Gracias por su ayuda. César Escalante C. [[alternative HTML version deleted]]

I did a RelWithDebInfo + asserts build of LLVM just now and, when running "make check" under Valgrind, am seeing a lot of uses of uninitialized memory like the one below. Anyone know offhand what's likely to be the root cause? Unfortunately a Debug build doesn't give these errors. Thanks, John FAIL: LLVM :: Analysis/BasicAA/pr18573.ll (2093 of 18733)

Buenas noches para cada uno. Me alegra saber que superamos los 200 usuarios y tengos expectativas con respecto a la I Conferencia de R-hispano en Murcia. No soy usuario de Linux por desconocimiento, algo que lamento. Debo instalar R en un equipo con Windows 7 a 64 bits. ¿Podrían indicarme por favor cómo instalarlo? ¿Se hace con el mismo archivo R-2.10.0-win32? ¿Debo cuidar o cambiar algo antes o

Buenas noches para cada uno. Me alegra saber que superamos los 200 usuarios y tengos expectativas con respecto a la I Conferencia de R-hispano en Murcia. No soy usuario de Linux por desconocimiento, algo que lamento. Debo instalar R en un equipo con Windows 7 a 64 bits. ¿Podrían indicarme por favor cómo instalarlo? ¿Se hace con el mismo archivo R-2.10.0-win32? ¿Debo cuidar o cambiar algo antes o

Well, it looks like almost all of the problems go away when I build using trunk instead of 3.9. So, that was scary but I'm going to forget it ever happened. >8000 test cases failed under Valgrind!! John On 11/20/2016 03:03 AM, Sanjoy Das via llvm-dev wrote: > Hi John, > > This is probably somewhat of a stretch, but since the problem does not > happen with a Debug build,

Reciban un saludo cordial. Por favor, ¿en cuál biblioteca de R existe una función para generar vectores aleatorios correlacionados, por ejemplo (X,Y), con X~Weibull y Y~Lognormal y corr(X,Y) = 0.7? Gracias desde ya por su atención/ayuda. César Escalante C. [[alternative HTML version deleted]]

Reciban un cordial saludo. De manera muy comedida les pido ayuda con la función indicada abajo. La usan en un artículo de inventarios. No veo dónde estoy errado. Gracias de antemano. César Escalante C. > lamb<-50 > L<-1 > h.<-10 > p<-25 > K<-5 > integ<-function(y){integrate(function(x)ppois(x,lamb*L),0,y)$value} > G<-function(y){(h.+p)*integ(y) +

Hi, I was building LLVM with gcc 6.1.1 recently and it was spitting out some warnings relating to misleading indention that caught my eye. This wasn't a fresh build so I may have missed some. I've CC'ed the authors of the potentially misleading lines so they can decide what do about the warnings (if anything). I'm wondering if clang-format is making some inappropriate choices

On Wed, Jun 6, 2012 at 3:09 AM, Joey Gouly <joel.gouly at gmail.com> wrote: > There are plans to upload, when Chandler has the time. The YouTube account > is LLVMProject. > Should get them up this week. Sorry I didn't even remember to do it after they were posted! > Joey > On Jun 6, 2012 8:45 AM, "ankur deshwal" <a.s.deshwal at gmail.com> wrote: >