search for: errorstr

Hi, In ExecutionEngine.cpp, when the JIT or the Interpreter have not been linked in then EngineBuilder::create fails without setting ErrorStr. I've attached a patch to fix this. Warm Regards KS Sreeram -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ee-not-linked-in-msg.diff URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090923/a455bb75/attachment.ksh>

...ndefined symbols (using SearchForAddressOfSymbol). I propose adding an extra parameter to the function definition, defaulting to true. static ExecutionEngine *create(ModuleProvider *MP, bool ForceInterpreter = false, std::string *ErrorStr = 0, bool Fast = false, bool EnumModules = true); And corresponding change to the function. ExecutionEngine *ExecutionEngine::create(ModuleProvider *MP, bool ForceInterpreter,...

...g problem when I try to debug "target does not support mc emission" in linux (the same code executes OK in windows): Below is a snippet extracted from this method, if (UseMCJIT && ExecutionEngine::MCJITCtor) { ExecutionEngine *EE = ExecutionEngine::MCJITCtor(M, ErrorStr, JMM, OptLevel, AllocateGVsWithCode, TM); if (EE) return EE; } else if (ExecutionEngine::JITCtor) { ExecutionEngine *EE = ExecutionEngine::JITCtor(M, ErrorStr, JMM, OptLevel, AllocateGVsWithCode,...

On Jul 22, 2009, at 5:23 PM, Chris Lattner wrote: > > On Jul 22, 2009, at 1:32 PM, Dan Gohman wrote: > >>>> >>>> - A null pointer is associated with no addresses. >>>> >>> >>> A null pointer in address space 0. >> >> I'm not fond of weird address-space semantics, but for consistency >> with what the optimizer is

.... I'd rather not. The current API is messy enough already. Is there not another way to solve the problem? Evan > > static ExecutionEngine *create(ModuleProvider *MP, > bool ForceInterpreter = false, > std::string *ErrorStr = 0, > bool Fast = false, > bool EnumModules = true); > > And corresponding change to the function. > > ExecutionEngine *ExecutionEngine::create(ModuleProvider *MP, > bool Fo...

...nt API is messy enough already. Is there not > another way to solve the problem? > > Evan > >> >>  static ExecutionEngine *create(ModuleProvider *MP, >>                                 bool ForceInterpreter = false, >>                                 std::string *ErrorStr = 0, >>                                 bool Fast = false, >>                                 bool EnumModules = true); >> >> And corresponding change to the function. >> >> ExecutionEngine *ExecutionEngine::create(ModuleProvider *MP, >>                    ...

...nt API is messy enough already. Is there not > another way to solve the problem? > > Evan > >> >>  static ExecutionEngine *create(ModuleProvider *MP, >>                                 bool ForceInterpreter = false, >>                                 std::string *ErrorStr = 0, >>                                 bool Fast = false, >>                                 bool EnumModules = true); >> >> And corresponding change to the function. >> >> ExecutionEngine *ExecutionEngine::create(ModuleProvider *MP, >>                    ...

...n LLVM-based project that is working on Linux up on Win32. I am having problems with llvm::ExecutionEngine::create returning a NULL. I traced it to these lines: // Unless the interpreter was explicitly selected, try making a JIT. if (!ForceInterpreter && JITCtor) EE = JITCtor(MP, ErrorStr); // If we can't make a JIT, make an interpreter instead. if (EE == 0 && InterpCtor) EE = InterpCtor(MP, ErrorStr); JITCtor and InterpCtor are both NULL, so it's obvious why I'm getting back a NULL execution engine. I am pretty sure it's because I'm missing a...

Hi all, Writing my own LLVM client I've noticed a potential null pointer dereference in EngineBuilder::selectTarget. The class has an optional pointer to the ErrorStr, which can be initialzied through setErrorStr() method. Although, it's strictly optional, selectTarget doesn't verify its value before assignment. Please find patch for branch release_31, revision 155051 attached. - Yury -------------- next part -------------- An HTML attachment was scrub...

...ing seemingly odd SegFaults when writing out using a raw_fd_ostream in the current trunk (last version worked, believe it was 153818, or similar). Again, nothing in the release notes... should I be scanning the svn log? For example, I have something like: raw_fd_ostream fout("out.txt", errorStr=""); .... fout<<"Hello World, how are you!"\n"; and it'll write out to the file, "Hello Wor" and then seg fault without assert. Sadly, this only happens for certain C code, any idea why this might be occuring? Also, during build I get a lot of these w...

I found a private ErrorStr member, but didn't find the get function of this member, could you tell me how I can get the error message? On Wed, Sep 18, 2019 at 4:02 PM mayuyu.io <admin at mayuyu.io> wrote: > Isn’t there a method in EngineBuilder to get the error message or > something? > I assume it’s you...

...de file. But I got a "corrupted double-linked list" error when "my llvm-as" works,however,when I do nothing on the disassembled bitcode file,everything is OK, After debugged,I found the error line is "MemoryBuffer *F = MemoryBuffer::getFileOrSTDIN(Filename.c_str(), &ErrorStr);" in the "Module *llvm::ParseAssemblyFile(const std::string &Filename, SMDiagnostic &Err,LLVMContext &Context)" function, I don't know the reason,anyone once got the similar trouble? Thanks

...eanly to trunk. Do you have commit access? Regards, -Jim On May 9, 2012, at 3:40 PM, Yury Mikhaylov wrote: > Hi all, > > Writing my own LLVM client I've noticed a potential null pointer dereference in EngineBuilder::selectTarget. > > The class has an optional pointer to the ErrorStr, which can be initialzied through setErrorStr() method. Although, it's strictly optional, selectTarget doesn't verify its value before assignment. > > Please find patch for branch release_31, revision 155051 attached. > > - Yury > > <TargetSelect.patch>___________...

...egards, > -Jim > > On May 9, 2012, at 3:40 PM, Yury Mikhaylov wrote: > > > Hi all, > > > > Writing my own LLVM client I've noticed a potential null pointer > dereference in EngineBuilder::selectTarget. > > > > The class has an optional pointer to the ErrorStr, which can be > initialzied through setErrorStr() method. Although, it's strictly optional, > selectTarget doesn't verify its value before assignment. > > > > Please find patch for branch release_31, revision 155051 attached. > > > > - Yury > > > >...

...er is being called. If I break in ExecutionEngine::create, I can see that UseMCJIT is true and ExecutionEngine::MCJITCtor is non-zero. Still at this point (lines after 481): if (UseMCJIT && ExecutionEngine::MCJITCtor) { ExecutionEngine *EE = ExecutionEngine::MCJITCtor(M, ErrorStr, JMM, AllocateGVsWithCode, TheTM.take()); if (EE) return EE; } else if (ExecutionEngine::JITCtor) { ExecutionEngine *EE = ExecutionEngine::JITCtor(M, ErrorStr, JMM, AllocateGVsWithCode, TheTM.take());...

...is related to lli using dlopen() with a NULL path to resolve symbols for the main program (lli program) itself. This happens when lli initially tries to create an ExecutionEngine ("EE = builder.create();" in lli.cpp), which leads to "if (sys::DynamicLibrary::LoadLibraryPermanently(0, ErrorStr)" in ExecutionEngine.cpp. Could anyone tell me how to resolve this? Thanks in advance! Toan Mai. -- View this message in context: http://old.nabble.com/Running-LLVM-JIT-on-qemu-system-arm-tp33763272p33763272.html Sent from the LLVM - Dev mailing list archive at Nabble.com.

...writing out using a > raw_fd_ostream in the current trunk (last version worked, believe it was > 153818, or similar). Again, nothing in the release notes... should I be > scanning the svn log? > > For example, I have something like: > > raw_fd_ostream fout("out.txt", errorStr=""); > .... > fout<<"Hello World, how are you!"\n"; > > and it'll write out to the file, "Hello Wor" and then seg fault without > assert. > > Sadly, this only happens for certain C code, any idea why this might be > occuring? >...

...094 #9 0x0036f6a8 in llvm::JIT::JIT (this=0x53956b0, MP=0x5395170, tm=@0x21ec400, tji=@0x21ec588, JMM=0x0) at JIT.cpp:101 #10 0x0036f6e9 in llvm::JIT::JIT (this=0x53956b0, MP=0x5395170, tm=@0x21ec400, tji=@0x21ec588, JMM=0x0) at JIT.cpp:102 #11 0x00375971 in llvm::JIT::createJIT (MP=0x5395170, ErrorStr=0x0, JMM=0x0) at TargetSelect.cpp:75 #12 0x0037667e in llvm::JIT::create (MP=0x5395170, Err=0x0) at JIT.h:76 #13 0x003648f8 in llvm::ExecutionEngine::create (MP=0x5395170, ForceInterpreter=false, ErrorStr=0x0) at ExecutionEngine.cpp:322 #14 0x003649b2 in llvm::ExecutionEngine::create (M=0x1902d...

...ode Emitter' on function '@__construct_Byte__Integer' The library is running on the Android device which has a cortex-9 CPU. The library usage to generate the machine code is: std::string errStr; llvm::EngineBuilder builder( module.get() ); builder.setErrorStr( &errStr ); builder.setEngineKind( llvm::EngineKind::JIT ); std::auto_ptr<llvm::ExecutionEngine> executionEngine( builder.create() ); llvm::Function *llvmEntry = module->getFunction( "entry" ); void (*entryPtr)() = (void (*)())executionEngine...

...; raw_fd_ostream in the current trunk (last version worked, believe it was >> 153818, or similar). Again, nothing in the release notes... should I be >> scanning the svn log? >> >> For example, I have something like: >> >> raw_fd_ostream fout("out.txt", errorStr=""); >> .... >> fout<<"Hello World, how are you!"\n"; >> >> and it'll write out to the file, "Hello Wor" and then seg fault without >> assert. >> >> Sadly, this only happens for certain C code, any idea why this...