search for: addmodule

...fine in LLVM 4, but I'm getting a compile error with LLVM 5. I think the problem is that this layer hasn't been modified to account for some of the changes made in LLVM 5, but I wanted to make sure that I wasn't missing something. I have code which looks like this: ModuleHandle addModule(std::unique_ptr<Module> M) { // Build our symbol resolver: // Lambda 1: Look back into the JIT itself to find symbols that are part of // the same "logical dylib". // Lambda 2: Search for external symbols in the host process. auto Re...

LTOCodeGenerator::addModule (which is wrapped by lto_codegen_add_module) takes an LTOModule as an argument and links the latter's llvm::Module into its own. It does not change the latter's llvm::Module. The lto_module_dispose API call destroys an LTOModule. This frees the LTOModule's llvm::Module, but also inval...

Hello, Has anybody experienced any problems with php3+php4 combo in systems newer than 4.6-STABLE (as of June-Aug 2002)? Briefly, the problem looks very similar to what is stated in the following reports: http://groups.google.com/groups?q=%22php3+kills+apache%22&hl=ru&lr=&ie=UTF-8&oe=UTF-8&selm=wqz8yrfzbug.wl%40hurt.theclones.net&rnum=1

...error > with LLVM 5. I think the problem is that this layer hasn’t been modified > to account for some of the changes made in LLVM 5, but I wanted to make > sure that I wasn’t missing something. > > > > I have code which looks like this: > > > > ModuleHandle addModule(std::unique_ptr<Module> M) { > > // Build our symbol resolver: > > // Lambda 1: Look back into the JIT itself to find symbols that > are part of > > // the same "logical dylib". > > // Lambda 2: Search for external...

Hi Johan, ld64 only calls functions from llvm/include/llvm-c/lto.h (defined in llvm/tools/lto/lto.cpp) For instance ThinLTOCodeGenerator::addModule is called through thinlto_codegen_add_module(). Apple hasn't released the code for ld64 in Xcode 9 yet, did you check if it is fixed in Xcode 9? (I think I remember fixing it in ld64 but I'm not totally sure...). >From what I can see with Xcode 8.2, the linker just passes the file name...

...; wrote: > > On Thu, Sep 7, 2017 at 5:44 PM, Mehdi AMINI <joker.eph at gmail.com> wrote: > >> Hi Johan, >> >> ld64 only calls functions from llvm/include/llvm-c/lto.h (defined >> in llvm/tools/lto/lto.cpp) >> >> For instance ThinLTOCodeGenerator::addModule is called >> through thinlto_codegen_add_module(). >> >> Apple hasn't released the code for ld64 in Xcode 9 yet, did you check if >> it is fixed in Xcode 9? >> (I think I remember fixing it in ld64 but I'm not totally sure...). >> > > I haven't...

...nfo block is stored at the top level. The next step is to think about what the API would look like for reading and writing multiple modules. Here's what I have in mind. To create a multi-module bitcode file, you would create a BitcodeWriter object and add modules to it: BitcodeWriter W(OS); W.addModule(M1); W.addModule(M2); W.write(); Reading a multi-module bitcode file would be supported with a BitcodeReader class. Each of the functional reader APIs in ReaderWriter.h would have a member function on BitcodeReader. We would also have a next() member function which would move to the next module in...

Hi! ExecutionEngine::addModule seems the method I have to use when I want to dynamically load snippets of code (e.g. containing a function) and execute them. I wonder why ExecutionEngine::create is only available with an initial module. I'd like to create an empty ExecutionEngine (i.e. without module) and then later use a...

...e: > >> 1) Can 0 ever be a valid VModuleKey? How can one reliably detect an invalid VModuleKey? > > > I believe 0 was a valid VModuleKey in ORCv1. The assertion is checking the the VModuleKey is present in the LogicalDylibs map. That means that you have to have used that key in an addModule call, e.g.: > > CODLayer.addModule(K, std::move(M)); > > and not subsequently removed the key with a call to removeModule. Yes indeed that is what happened. So to prevent that I need to check if VModuleKey was ever initialized ... how do I do that? I would have to have to add another f...

...some tiny changes to the front end to deal with some slight API changes introduced in the JIT tutorial where some functions return Expected. For example, the specific place that this is failing: FnIR->print(errs()); fprintf(stderr, "\n"); - TheJIT->addModule(std::move(TheModule)); + auto add_q = TheJIT->addModule(std::move(TheModule)); + assert(add_q && "HandleDefinition: Error adding a module."); InitializeModuleAndPassManager(); I've looked at a previous thread discussing moving from ORCv1 to O...

...i AMINI <joker.eph at gmail.com> wrote: >>> >>>> Hi Johan, >>>> >>>> ld64 only calls functions from llvm/include/llvm-c/lto.h (defined >>>> in llvm/tools/lto/lto.cpp) >>>> >>>> For instance ThinLTOCodeGenerator::addModule is called >>>> through thinlto_codegen_add_module(). >>>> >>>> Apple hasn't released the code for ld64 in Xcode 9 yet, did you check >>>> if it is fixed in Xcode 9? >>>> (I think I remember fixing it in ld64 but I'm not totally sur...

...tions. We would provide, either in LLVM or LLDB, debug info parsers that wrap this class to parse the contained debug info. My intent is that use of this API would look something like: ExecutionEngine EE = ...; DebugInfoListener DI = new DebugInfoListener(...); EE->addEventListener(DI); EE->addModule(Foo); EE->addModule(Bar); MCJITDebugInfoParser DIP = createMCJITDebugInfoParser(DI); DIP...; Any thoughts/comments on this (admittedly very vague) proposal are very welcome. Assuming it sounds reasonable so far, I'm going to start hacking up some patches and basic use cases to serve as a b...

...e top level. The next step is to think about what the API would look like for reading and writing multiple modules. > > Here's what I have in mind. To create a multi-module bitcode file, you would create a BitcodeWriter object and add modules to it: > > BitcodeWriter W(OS); > W.addModule(M1); > W.addModule(M2); > W.write(); That requires the two modules to lives longer than the bitcode write, the API could be: BitcodeWriter W(OS); W.writeModule(M1); // delete M1 // ... // create M2 W.writeModule(M2); (Maybe you had this in mind, but the API naming didn’t reflect it so I’m...

...fixed it on the lld side. >> > >> >> Yes, Teresa is right, this is the correct fix. >> I'm not sure what subset of GNU archives Mach-O supports, but the only >> way of being safe is using offset in the archive + archive name. > > > ThinLTOCodeGenerator::addModule is called by the linker, right? (I can't > find any callers) > When it is called, we cannot retrieve the offset of the module inside the > archive, because the linker didn't tell us about it. See here for the fix. https://reviews.llvm.org/D25495 You pass the the archive name + off...

Hi, I am getting following assertion failure when attempting to remove a module. /llvm/ExecutionEngine/Orc/CompileOnDemandLayer.h:311: llvm::Error llvm::orc::LegacyCompileOnDemandLayer<BaseLayerT, CompileCallbackMgrT, IndirectStubsMgrT>::removeModule(llvm::orc::VModuleKey) [with BaseLayerT =

...vel. The next step is to think > about what the API would look like for reading and writing multiple modules. > > Here's what I have in mind. To create a multi-module bitcode file, you > would create a BitcodeWriter object and add modules to it: > > BitcodeWriter W(OS); > W.addModule(M1); > W.addModule(M2); > W.write(); > > > That requires the two modules to lives longer than the bitcode write, the > API could be: > > BitcodeWriter W(OS); > W.writeModule(M1); > // delete M1 > // ... > // create M2 > W.writeModule(M2); > > (Maybe you...

...t;>> >>>>>> Hi Johan, >>>>>> >>>>>> ld64 only calls functions from llvm/include/llvm-c/lto.h (defined >>>>>> in llvm/tools/lto/lto.cpp) >>>>>> >>>>>> For instance ThinLTOCodeGenerator::addModule is called >>>>>> through thinlto_codegen_add_module(). >>>>>> >>>>>> Apple hasn't released the code for ld64 in Xcode 9 yet, did you check >>>>>> if it is fixed in Xcode 9? >>>>>> (I think I remember fixin...

...t;>> wrote: >>>> >>>>> Hi Johan, >>>>> >>>>> ld64 only calls functions from llvm/include/llvm-c/lto.h (defined >>>>> in llvm/tools/lto/lto.cpp) >>>>> >>>>> For instance ThinLTOCodeGenerator::addModule is called >>>>> through thinlto_codegen_add_module(). >>>>> >>>>> Apple hasn't released the code for ld64 in Xcode 9 yet, did you check >>>>> if it is fixed in Xcode 9? >>>>> (I think I remember fixing it in ld64 but I...

...>> slight API changes introduced in the JIT tutorial where some functions >> return Expected. For example, the specific place that this is failing: >> >> FnIR->print(errs()); >> fprintf(stderr, "\n"); >> - TheJIT->addModule(std::move(TheModule)); >> + auto add_q = TheJIT->addModule(std::move(TheModule)); >> + assert(add_q && "HandleDefinition: Error adding a module."); >> InitializeModuleAndPassManager(); >> >> >> I've looked at...