search for: ismaterializ

...azy loaded, but that would explain the question then > :) > > Neil: can you clarify? If Teresa is right, why aren't you materializing > the destination module entirely? > > I don't think it has ever been tried to use a lazy destination. Having said that, I don't think isMaterializable should return true for a declaration. > Even materializing functions from the source module on the fly isn't > supported right now, is it? > > It is. Neil, the flag is linked to llvm-link's -only-needed command line option. At least for simple cases it seems to be working...

...question then :) > > Neil: can you clarify? If Teresa is right, why aren't you > materializing the destination module entirely? > > > > I don't think it has ever been tried to use a lazy destination. > Having said that, I don't think isMaterializable should return > true for a declaration. > > > Looking at isMaterializable, I'm now a little confused about Neil's > case - the materializable bit is set to true only when > the MODULE_CODE_FUNCTION indicated that it was !isproto, which means > it should have...

...copied over during linking. The only line of code that differs when you set LinkOnlyNeeded is in LinkModules.cpp -> ModuleLinker::linkIfNeeded: if (shouldLinkOnlyNeeded() && !(DGV && DGV->isDeclaration())) return false; The isDeclaration() for functions has a call to isMaterializable(). Things I've tried: * If I don't pass LinkOnlyNeeded but still link from the lazily loaded runtime module into the user module, it works (albeit it is orders of magnitude slower like we'd expect). * If I don't lazily load the runtime module, it works (but again,...

...he only line of code that differs when you set LinkOnlyNeeded is in > LinkModules.cpp -> ModuleLinker::linkIfNeeded: > > if (shouldLinkOnlyNeeded() && !(DGV && DGV->isDeclaration())) > return false; > > > The isDeclaration() for functions has a call to isMaterializable(). > > Things I've tried: > > - If I don't pass LinkOnlyNeeded but still link from the lazily loaded > runtime module into the user module, it works (albeit it is orders of > magnitude slower like we'd expect). > - If I don't lazily load the runt...

...} (gdb) br llvm::AssemblyWriter::printModule(llvm::Module const*) (gdb) p m_CurTransaction->getModule()->dump() llvm::AssemblyWriter::printGlobal (this=0x7fff5fbfe850, GV=0x107274058) at /Users/vvassilev/workspace/root/interpreter/llvm/src/lib/IR/AsmWriter.cpp:1444 1444 if (GV->isMaterializable()) (gdb) p GV->use_empty() $78 = false (gdb) p GV->use_back() $79 = (class llvm::User *) 0x107279b88 (gdb) p GV->use_back()->dump() i8* getelementptr inbounds ([21 x i8]* @.str1, i32 0, i32 0) $80 = void (gdb) p (('llvm::Instruction'*)GV->use_back()) $81 = ('llvm::Ins...

...vm::AssemblyWriter::printModule(llvm::Module const*) > (gdb) p m_CurTransaction->getModule()->dump() > llvm::AssemblyWriter::printGlobal (this=0x7fff5fbfe850, GV=0x107274058) at > /Users/vvassilev/workspace/root/interpreter/llvm/src/lib/IR/AsmWriter.cpp:1444 > 1444 if (GV->isMaterializable()) > (gdb) p GV->use_empty() > $78 = false > (gdb) p GV->use_back() > $79 = (class llvm::User *) 0x107279b88 > (gdb) p GV->use_back()->dump() > i8* getelementptr inbounds ([21 x i8]* @.str1, i32 0, i32 0) > $80 = void > (gdb) p (('llvm::Instruction'*)...

...tions, sees if they're from the loaded module, and then materializes them. Is this the best way to handle JITing code from a lazily loaded module or is there a better way to handle this? It seems like this could be handled easily by moveFunctionBody if it just did something like: if (OrigF.isMaterializable()) { OrigF.materialize(); } Is there a way to add a hook into the JIT to handle this kind of materialization? Thanks, Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161213/f30e917e/attach...

Thanks, I must have missed these, added. On Apr 22, 2010, at 1:28 AM, Matthieu Moy wrote: > Chris Lattner <clattner at apple.com> writes: > >> Ok, the LLVM 2.7 release notes are in near final shape. Please take >> a look and suggest improvements (or, better yet, just commit >> improvements if you have commit access): > > About the API changes, some that hit

...er::printModule(llvm::Module const*) >> (gdb) p m_CurTransaction->getModule()->dump() >> llvm::AssemblyWriter::printGlobal (this=0x7fff5fbfe850, GV=0x107274058) at >> /Users/vvassilev/workspace/root/interpreter/llvm/src/lib/IR/AsmWriter.cpp:1444 >> 1444 if (GV->isMaterializable()) >> (gdb) p GV->use_empty() >> $78 = false >> (gdb) p GV->use_back() >> $79 = (class llvm::User *) 0x107279b88 >> (gdb) p GV->use_back()->dump() >> i8* getelementptr inbounds ([21 x i8]* @.str1, i32 0, i32 0) >> $80 = void >> (gdb) p...