aboutsummaryrefslogtreecommitdiff
path: root/llvm/tools/llvm-objdump/llvm-objdump.cpp
diff options
context:
space:
mode:
authorDavid Majnemer <david.majnemer@gmail.com>2014-11-11 08:43:57 +0000
committerDavid Majnemer <david.majnemer@gmail.com>2014-11-11 08:43:57 +0000
commit2cc4bc77bf11d465faf03b0ae0f5a623f0f73e70 (patch)
tree1b2f8b1e1f81b4c282266de81b55135ce022e2dc /llvm/tools/llvm-objdump/llvm-objdump.cpp
parentd158db0f63cece2520e0d70b8bd712001cd78322 (diff)
downloadllvm-2cc4bc77bf11d465faf03b0ae0f5a623f0f73e70.zip
llvm-2cc4bc77bf11d465faf03b0ae0f5a623f0f73e70.tar.gz
llvm-2cc4bc77bf11d465faf03b0ae0f5a623f0f73e70.tar.bz2
MC, COFF: Use relocations for function references inside the section
Referencing one symbol from another in the same section does not generally require a relocation. However, the MS linker has a feature called /INCREMENTAL which enables incremental links. It achieves this by creating thunks to the actual function and redirecting all relocations to point to the thunk. This breaks down with the old scheme if you have a function which references, say, itself. On x86_64, we would use %rip relative addressing to reference the start of the function from out current position. This would lead to miscompiles because other references might reference the thunk instead, breaking function pointer equality. This fixes PR21520. llvm-svn: 221678
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions