summaryrefslogtreecommitdiffstats
path: root/llvm/unittests/Support/TimerTest.cpp
diff options
context:
space:
mode:
authorEd Schouten <ed@nuxi.nl>2016-04-05 20:17:33 +0000
committerEd Schouten <ed@nuxi.nl>2016-04-05 20:17:33 +0000
commitf2fdd013a29b26791490e3a33beda1bacfeec182 (patch)
tree5cc67b915027ef65e09dd46f1541a60e12233e5d /llvm/unittests/Support/TimerTest.cpp
parent60fbd3bdb78c0b220f63fa886c877ac7adc6bca7 (diff)
downloadbcm5719-llvm-f2fdd013a29b26791490e3a33beda1bacfeec182.tar.gz
bcm5719-llvm-f2fdd013a29b26791490e3a33beda1bacfeec182.zip
Don't omit dynamic relocations for the GOT.
Where Clang's AArch64 backend seems to differ from the X86 backend is that it tends to use the GOT more aggressively. After getting CloudABI PIEs working on x86-64, I noticed that accessing global variables would still crash on aarch64. Tracing it down, it turns out that the GOT was filled with entries assuming the base address was zero. It turns out that we skip generating relocations for GOT entries in case the relocation pointing towards the GOT is relative. Whether the thing pointing to the GOT is absolute or relative shouldn't make any difference; the GOT entry itself should contain the absolute address, thus needs a relocation regardless. Approved by: rafael Differential Revision: http://reviews.llvm.org/D18739 llvm-svn: 265453
Diffstat (limited to 'llvm/unittests/Support/TimerTest.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud