forked from OSchip/llvm-project
a2639dcbe6
If a tool wants to introduce new indirections via stubs at link-time in ORC, it can cause fidelity issues around the address of the function if some references to the function do not have relocations. This is known to happen inside the body of the function itself on x86_64 for example, where a PC-relative address is formed, but without a relocation. ``` _foo: leaq -7(%rip), %rax ## form pointer to '_foo' without relocation _bar: leaq (%rip), %rax ## uses X86_64_RELOC_SIGNED to '_foo' ``` The consequence of introducing a stub for such a function at link time is that if it forms a pointer to itself without relocation, it will not have the same value as a pointer from outside the function. If the function pointer is used as a key, this can cause problems. This utility provides best-effort support for adding such missing relocations using MCDisassembler and MCInstrAnalysis to identify the problematic instructions. Currently it is only implemented for x86_64. Note: the related issue with call/jump instructions is not handled here, only forming function pointers. rdar://83514317 Differential revision: https://reviews.llvm.org/D113038 |
||
|---|---|---|
| .. | ||
| IntelJITEvents | ||
| Interpreter | ||
| JITLink | ||
| MCJIT | ||
| OProfileJIT | ||
| Orc | ||
| PerfJITEvents | ||
| RuntimeDyld | ||
| CMakeLists.txt | ||
| ExecutionEngine.cpp | ||
| ExecutionEngineBindings.cpp | ||
| GDBRegistrationListener.cpp | ||
| SectionMemoryManager.cpp | ||
| TargetSelect.cpp | ||