search for: geterror

...(char) 0xde) std::cout << "0xde ok\n"; llvm::MemoryBuffer* mbjit = llvm::MemoryBuffer::getMemBufferCopy (sr); llvm::ErrorOr<llvm::Module*> ModuleOrErr = llvm::parseBitcodeFile (mbjit, context); if (llvm::error_code EC = ModuleOrErr.getError()) { std::cout << ModuleOrErr.getError().message() << "\n"; } Module* Mjit = ModuleOrErr.get(); std::string eeError; ExecutionEngine* nee = EngineBuilder(Mjit).setEngineKind(EngineKind::JIT).setUseMCJIT(true).setErrorStr(&eeError).create(); if (!nee) { fprintf(s...

...something wrong with your code in "3:", i.e.: > > MemoryBuffer* mbjit = MemoryBuffer::getMemBuffer (sr.str()); > LLVMContext& context = getGlobalContext(); > ErrorOr<Module*> ModuleOrErr = parseBitcodeFile (mbjit, context); > if (error_code EC = ModuleOrErr.getError()) > { > std::cout << ModuleOrErr.getError(). > message() << "\n"; > assert(false); > } > > Can you post how you modified it in your second reply? For debugging purpose, you can simply use MemoryBuffer::getMemBufferCopy() and not worry about v...

...and > do things like informing MemoryBuffer that this is the case. > > Hope this helps, > ~Will > >> LLVMContext& context = getGlobalContext(); >> ErrorOr<Module*> ModuleOrErr = parseBitcodeFile (mbjit, context); >> if (error_code EC = ModuleOrErr.getError()) >> { >> std::cout << ModuleOrErr.getError().message() << "\n"; >> assert(false); >> } >> >> >> >> >> This is the execution result: >> B ok >> C ok >> 0xc0 ok >> 0xde ok >> In...

...xde) std::cout << "0xde ok\n"; 3) I try to parse the gv by MemoryBuffer* mbjit = MemoryBuffer::getMemBuffer (sr.str()); LLVMContext& context = getGlobalContext(); ErrorOr<Module*> ModuleOrErr = parseBitcodeFile (mbjit, context); if (error_code EC = ModuleOrErr.getError()) { std::cout << ModuleOrErr.getError().message() << "\n"; assert(false); } This is the execution result: B ok C ok 0xc0 ok 0xde ok Invalid bitcode signature Ok is not working :/ But why ??? For debuging, between 2) and 3), I export the readed module and...

...std::cout << "0xde ok\n"; >> llvm::MemoryBuffer* mbjit = llvm::MemoryBuffer::getMemBufferCopy (sr); >> >> llvm::ErrorOr<llvm::Module*> ModuleOrErr = llvm::parseBitcodeFile >> (mbjit, context); >> if (llvm::error_code EC = ModuleOrErr.getError()) { >> std::cout << ModuleOrErr.getError().message() << "\n"; >> } >> >> Module* Mjit = ModuleOrErr.get(); >> >> std::string eeError; >> ExecutionEngine* nee = >> EngineBuilder(Mjit).setEngineKind(EngineKind::JIT).setUseMCJIT(tr...

...mbolRef class. On iOS, the number returned is not always correct (some function have the right size). Sadly, This is my code (at the end of the main function into driver.cpp) : #### ErrorOr<OwningBinary<Binary>> BinaryOrErr = createBinary(file); if (std::error_code ec = BinaryOrErr.getError()) { return ec.value(); } Binary &Binary = *BinaryOrErr.get().getBinary(); object::ObjectFile *objfile; objfile = dyn_cast<ObjectFile>(&Binary); for (const SymbolRef &Symbol : objfile->symbols()) { uint64_t size; Symbol.getAddress(size); } #### During my previous sear...

...Binary name of the generated class...")); int main(int argc, char** argv) { cl::ParseCommandLineOptions(argc, argv, "Hi.."); LLVMContext context; ErrorOr<unique_ptr<MemoryBuffer>> mb = MemoryBuffer::getFile(input); if(error_code ec = mb.getError()) { errs() << ec.message(); return 1; } Expected<unique_ptr<Module>> m = parseBitcodeFile(mb->get()->getMemBufferRef(),context); if(error_code ec= errorToErrorCode(m.takeError()) ) { PassManage...

...exit, all memory pools and all global variables I am very opposed to it. lld is an actual project with actual value for its users. I really don't want to compromise its maintainability by turning every for (auto &X : check(...)) into auto XsOrErr = ...; if (std::error_code EC = XsOrErr.getError()) return EC; // also update callers. Add more context to the return if // you don't want to degrade the error message. auto &Xs = *XsOrErr; for (auto &X : Xs) In the name of a theoretical user. Really, can we put this on hold until the MachO linker has shown how to get...

...r** argv) >> { >> cl::ParseCommandLineOptions(argc, argv, "Hi.."); >> LLVMContext context; >> >> >> ErrorOr<unique_ptr<MemoryBuffer>> mb = >> MemoryBuffer::getFile(input); >> if(error_code ec = mb.getError()) >> { >> errs() << ec.message(); >> return 1; >> } >> >> Expected<unique_ptr<Module>> m = >> parseBitcodeFile(mb->get()->getMemBufferRef(),context); >> if(error_...

...ectAuth defaultAuth = new ConnectAuthDefault(); try{ conn = new Connect("xenapi://root at 192.168.1.23?no_verify=1", defaultAuth, 0); } catch (LibvirtException e){ System.out.println("exception caught:"+e); System.out.println(e.getError()); } try { Domain testDomain=conn.domainLookupByName("DeviceSimulator (192.168.1.150)"); System.out.println("Domain:" + testDomain.getName() + " id " + testDomain.getID() + " running " +...

I have a WxRuby application that takes a few inputs from the user and uses that information to search through a large file for matches. The application works very well, with one exception. If I click anywhere in the frame while the application is searching through the long file, the application hangs. Has anyone experienced anything similar to this? Any suggestions on how I can fix this? Thanks

...ay be a build script problem. However, based on earlier reports of runtime version incompatibilities, it was looking like I was going to have to recompile a *lot* of code. The discussion today suggested that as long as function accesses are used and not variable accesses, things will be okay (e.g., GetError() in Windows, not errno). The problem, as I pointed out to them, is that *most* Unix developers only ever have to worry about a single C runtime being on their system and therefore don''t need to worry about errno being in a different runtime DLL. Ideally, they would be able to give us an e...

...F itself). -- Sean Silva > > lld is an actual project with actual value for its users. I really don't > want to compromise its maintainability by turning every > > for (auto &X : check(...)) > > into > > auto XsOrErr = ...; > if (std::error_code EC = XsOrErr.getError()) > return EC; // also update callers. Add more context to the return if > // you don't want to degrade the error message. > auto &Xs = *XsOrErr; > for (auto &X : Xs) > > In the name of a theoretical user. Really, can we put this on hold > until the...

On Tue, August 9, 2016 11:51 am, Gordon Messmer wrote: > On 08/08/2016 11:11 PM, Alessandro Baggi wrote: >> | 78 | backup-fd | 2016-08-08 09:52:57 | B | F | 191,024 | >> 7,978,295,072 | T | >> >> | 79 | backup-fd | 2016-08-08 12:10:31 | B | F | 0 | >> 0 | A | >> >> | 80 | backup-fd | 2016-08-09 03:05:03 |

...splayFilename = InputFilename; > ErrorOr<std::unique_ptr<Module>> MOrErr = > - getStreamedBitcodeModule(DisplayFilename, Streamer, Context); > + getStreamedBitcodeModule(DisplayFilename, std::move(Streamer), Context); > if (std::error_code EC = MOrErr.getError()) > ErrorMessage = EC.message(); > else > M = std::move(*MOrErr); > if(M.get()) { > + errs() << "foobar " << Foo.getMaxPos() << '\n'; Debug output? > if (std::error_code EC = M->materializeAllPermanently...

.... setError(make_pair(blah_error::unkown_reloc, vector<string>{relocationumer, loc})); // loc could be calculated by backtracking, or just the current file address. (we could even pass the address as a stop address to obj2yaml). // Someplace else. if (File->error()) o << File->getErrorMessage(); Which would do the string substitution. This lets us not spend any time building up a representation for diagnostics when none will be printed, and still get decent diagnostics with well defined enum values when needed. So: virtual std::unique_ptr<lld::File> readFile(StringRef p...

...setup region with normal control flow. In this case, the Clang should emit a normal cleanup to call `llvm.eh.teardown`. Consider: ```c++ #define RETURN_IF_ERR(maybeError) \ ({ \ auto val = maybeError; \ if (val.isError()) \ return val.getError(); \ val.getValue; \ }) ErrorOr<int> mayFail(); void use_callsetup(int, Foo); void f(bool cond) { use_callsetup(RETURN_IF_ERR(mayFail()), Foo()); } ``` ### Inlining non-EH code into EH code If exceptions are disabled, the frontend should not emit exceptional cle...

...auto ReloadedBufferOrErr = CacheEntry.tryLoadingBuffer(); <-The explanation says this is done to reduce the memory pressure. But it’s not clear to me why this helps to reduce memory pressure, since we still have to keep if (auto EC = ReloadedBufferOrErr.getError()) { <- the content of the cache file in a buffer, pointed to by ReloadedBufferOrErr). // On error, keeping the preexisting buffer and printing a // diagnostic is more friendly than just crashing. errs() &l...

I talked several people and found that this is more like a communication issue rather than a technical/philosophical issue. I believe communication problems won't solve themselves. As a person who is on the owners file of LLD, I think I need to say something about that issue. Also, I guess people who were just watching this thread wondered why my happy pre-holiday status report suddenly turned

...auto ReloadedBufferOrErr = CacheEntry.tryLoadingBuffer(); > <-The explanation says this is done to reduce the memory pressure. But it’s > not clear to me why this helps to reduce memory pressure, since we still > have to keep > > if (auto EC = ReloadedBufferOrErr.getError()) > { <- the content of the > cache file in a buffer, pointed to by ReloadedBufferOrErr). > > // On error, keeping the preexisting buffer and printing a > > // diagnostic is more friendly than just cra...