search for: gotentri

...d at Addr+2 } return Addr; } @@ -473,6 +480,7 @@ void RuntimeDyldImpl::resolveExternalSym // MemoryManager. uint8_t *Addr = (uint8_t*) MemMgr->getPointerToNamedFunction(Name.data(), true); + updateGOTEntries(Name, (uint64_t)Addr); DEBUG(dbgs() << "Resolving relocations Name: " << Name << "\t" << format("%p", Addr) << "\n"); Modified: llvm/trunk/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldE...

...is no guarantee that the loaded object files are allocated within 2GB of each other in memory. What was the intended use case of this feature? Additionally, it seems that currently every access through the GOT get it's own entry, when identical relocations could be combined into one entry. The GOTEntries array is also never cleared, causing memory and performance problems when loading multiple object files (this is a bug and easily fixed, but makes me think this feature isn't particularly well tested). I'm planning to redesign the GOT mechanism, but I would like to understand the use case...