search for: moduleb

Hi all, I'm trying to use a function defined in one LLVM module from another module (in the JIT) but for some reason it's not working out. My sequence of activity is roughly like this: 1) Create moduleA 2) Create moduleB with "func()" 3) execEng = ExecutionEngine::create( new ExistingModuleProvider(moduleB)); 4) execute "func()" (this works fine) 4) add "func()" to moduleA as a declaration (no code blocks) with External linkage. 5) execEng->addModuleProvider(ne...

...LLVMContext& context = getGlobalContext(); llvm::raw_fd_ostream osA("A.bc", "", llvm::sys::fs::F_None); llvm::raw_fd_ostream osB("B.bc", "", llvm::sys::fs::F_None); llvm::Module *ModuleA = new llvm::Module("A", context); llvm::Module *ModuleB = new llvm::Module("B", context); ModuleA->setDataLayout(M.getDataLayout()); ModuleA-->setTargetTriple(M.getTargetTriple()); ModuleA-->setModuleInlineAsm(M.getModuleInlineAsm()); ModuleB-->setDataLayout(M.getDataLayout()); ModuleB-->setTargetTriple(M.getTargetTr...

Michael Muller wrote: > > Hi all, > > I'm trying to use a function defined in one LLVM module from another module > (in the JIT) but for some reason it's not working out. My sequence of > activity is roughly like this: > > 1) Create moduleA > 2) Create moduleB with "func()" > 3) execEng = ExecutionEngine::create( > new ExistingModuleProvider(moduleB)); > 4) execute "func()" (this works fine) > 4) add "func()" to moduleA as a declaration (no code blocks) with External > linkage. > 5) ex...

...; >> Hi all, >> >> I'm trying to use a function defined in one LLVM module from another module >> (in the JIT) but for some reason it's not working out.  My sequence of >> activity is roughly like this: >> >>   1) Create moduleA >>   2) Create moduleB with "func()" >>   3) execEng = ExecutionEngine::create( >>          new ExistingModuleProvider(moduleB)); >>   4) execute "func()" (this works fine) >>   4) add "func()" to moduleA as a declaration (no code blocks) with External >>      l...

...s there a preferred approach for an LLVM-based JIT-compiler to make calls from run-time generated functions in module A to bitcode-loaded functions in module B? A naive CallInst across the boundary fails verification. Calling it as an external function fails to resolve, even if both ModuleA and ModuleB are in the same ExecutionEngine. I can think of two ways around this: 1. Create a constant function pointer in ModuleA using the value from EE.getPointerToFunction(FunctionB). This seems trivial, but I am concerned it will prevent many optimizations. 2. Copy functions from ModuleB into ModuleA...

...s there a preferred approach for an LLVM-based JIT-compiler to make calls from run-time generated functions in module A to bitcode-loaded functions in module B? A naive CallInst across the boundary fails verification. Calling it as an external function fails to resolve, even if both ModuleA and ModuleB are in the same ExecutionEngine. I can think of two ways around this: 1. Create a constant function pointer in ModuleA using the value from EE.getPointerToFunction(FunctionB). This seems trivial, but I am concerned it will prevent many optimizations. 2. Copy functions from ModuleB into ModuleA...

...h the LLJIT as I finally understand, I will only get the addresses when I have resolved every references, which makes the code way safer. However, another thing of our system is, that each object file was loaded from a different process, so sometimes not all symbols for ModuleA were present because ModuleB was not loaded/requested yet. That was okay, so we kept resolving the undefined references of ModuleA until ModuleB was loaded and everything was fine. If I get it right… This would change now to having a single LLJIT representing the entire system. Each process would get it’s own DyLib for there...

...; >>> I'm trying to use a function defined in one LLVM module from another module >>> (in the JIT) but for some reason it's not working out. My sequence of >>> activity is roughly like this: >>> >>> 1) Create moduleA >>> 2) Create moduleB with "func()" >>> 3) execEng = ExecutionEngine::create( >>> new ExistingModuleProvider(moduleB)); >>> 4) execute "func()" (this works fine) >>> 4) add "func()" to moduleA as a declaration (no code blocks) with External...

...<div>I want to call some functions from another module (<strong>B</strong>);</div><div>I load module <strong>B</strong> withing the same LLVMContext, and create a function declaration in module A via:</div><div>    auto functionInAnotherModule = ModuleB.getFunction(callableName);</div><div>    auto functionType = functionInAnotherModule->getFunctionType();</div><div>    auto localFunction = llvm::Function::Create(functionType, llvm::GlobalValue::LinkageTypes::ExternalWeakLinkage, callableName, &ModuleA);</div>&...

...>> Hi all, >> >> I'm trying to use a function defined in one LLVM module from another module >> (in the JIT) but for some reason it's not working out. My sequence of >> activity is roughly like this: >> >> 1) Create moduleA >> 2) Create moduleB with "func()" >> 3) execEng = ExecutionEngine::create( >> new ExistingModuleProvider(moduleB)); >> 4) execute "func()" (this works fine) >> 4) add "func()" to moduleA as a declaration (no code blocks) with External >> linkag...

On 3 February 2010 14:13, Garrison Venn <gvenn.cfe.dev at gmail.com> wrote: > I have not used the C api or the interpreter, but via JIT one can use > ExecutionEngine::addGlobalMapping(...) after the function decl in the > foreign module. See if there is an equivalent in the C API, which will > probably work for the interpreter given that this method is declared in >

...ller at enduden.com> wrote: > > Hi all, > > I'm trying to use a function defined in one LLVM module from another module > (in the JIT) but for some reason it's not working out.  My sequence of > activity is roughly like this: > >  1) Create moduleA >  2) Create moduleB with "func()" >  3) execEng = ExecutionEngine::create( >         new ExistingModuleProvider(moduleB)); >  4) execute "func()" (this works fine) >  4) add "func()" to moduleA as a declaration (no code blocks) with External >     linkage. >  5) execEng-...

...h the LLJIT as I finally understand, I will only get the addresses when I have resolved every references, which makes the code way safer. However, another thing of our system is, that each object file was loaded from a different process, so sometimes not all symbols for ModuleA were present because ModuleB was not loaded/requested yet. That was okay, so we kept resolving the undefined references of ModuleA until ModuleB was loaded and everything was fine. If I get it right… This would change now to having a single LLJIT representing the entire system. Each process would get it’s own DyLib for there...

Hey everyone, I felt this question is different from my other question - hope this is okay. So - I was playing around with the lookup function of the ExecutionSession and there are some things I don't understand. I have a .BC file with a function "?Sampler@@YAXXZ" referencing a value "?_Plansch_test@@3HA" that is not defined in that module itself. I first planed on not

Hey all, A quick question about the LLVM C-Api and using LinkModules. In a normal situation where I have 2 LLVM modules and 1 depends on the other using LLVMLinkModules2() works perfectly. LLVMLinkModules2() "Links the source module into the destination module. The source module is destroyed." according to the comment of the function. That is all fine when you only have 2 modules. But

...h the LLJIT as I finally understand, I will only get the addresses when I have resolved every references, which makes the code way safer. However, another thing of our system is, that each object file was loaded from a different process, so sometimes not all symbols for ModuleA were present because ModuleB was not loaded/requested yet. That was okay, so we kept resolving the undefined references of ModuleA until ModuleB was loaded and everything was fine. If I get it right… This would change now to having a single LLJIT representing the entire system. Each process would get it’s own DyLib for there...

...I get ERROR: Program used external function 'myLinkedFunction' which could not be resolved! Because of its brevity, I use getOrInsertFunction when I am creating calls to the function in module A. I use new llvm::Function(type, llvm::Function::ExternalLinkage, "myLinkedFunction", moduleB) when I am defining the function with its body in module B. I then have an ExecutionEngine which I constructed with an empty dummy module so that I can use addModuleProvider and removeModuleProvider to link arbitrary modules later. I call addModuleProvider with module A and module B wrapped in Ex...

Hi dear Users, I''ve been looking in internet and on the puppet wiki website but i am still confused about this. Lets say I have 2 Modules: A and B What I want to do is call a class on module A directly from module B. I know it is possible to call different classes within a module by using inheritance and using different .pp config files. But how I do not know how to do the

Hi, I just put together a little mixin to provide pseudo-RESTful services in camping apps. Basically, it looks for a hidden _verb field in form posts, and sets the @method to the supplied value (e.g. put or delete - which browsers don''t support). This lets you define put and delete methods in your controllers. Groovy. Code: http://pastie.caboo.se/22613 Is there any permanent repo of

Hi group, im updating some modules of puppet, and i found this issue or error, that i cannot get resolved it. My puppetmaster is 2.7.1 and client 2.7.18. I used other modulo to prover apt configurations but i think this is more completed. I know that the error is something missing or my class is not present or something like that, the dependencies of the modulo are installed, stdlib and i