diff options
author | Fangrui Song <maskray@google.com> | 2019-06-20 14:00:08 +0000 |
---|---|---|
committer | Fangrui Song <maskray@google.com> | 2019-06-20 14:00:08 +0000 |
commit | 249fde85832c33f8b06c6b4ac65d1c4b96d23b83 (patch) | |
tree | 1af352336fe97e57ca3fced4b02a07afae6c1031 /clang/lib/Frontend/CompilerInvocation.cpp | |
parent | ffed2c96d9f1379a2af4b1b0827255da0be59d65 (diff) | |
download | llvm-249fde85832c33f8b06c6b4ac65d1c4b96d23b83.zip llvm-249fde85832c33f8b06c6b4ac65d1c4b96d23b83.tar.gz llvm-249fde85832c33f8b06c6b4ac65d1c4b96d23b83.tar.bz2 |
[ELF][ARM][AARCH64][MIPS][PPC] Simplify the logic to create R_*_RELATIVE for absolute relocation types in writable sections
Summary:
Our rule to create R_*_RELATIVE for absolute relocation types were
loose. D63121 made it stricter but it failed to create R_*_RELATIVE for
R_ARM_TARGET1 and R_PPC64_TOC. rLLD363236 worked around that by
reinstating the original behavior for ARM and PPC64.
This patch is an attempt to simplify the logic.
Note, in ld.bfd, R_ARM_TARGET2 --target2=abs also creates
R_ARM_RELATIVE. This seems a very uncommon scenario (moreover,
--target2=got-rel is the default), so I do not implement any logic
related to it.
Also, delete R_AARCH64_ABS32 from AArch64::getDynRel. We don't have
working ILP32 support yet. Allowing it would create an incorrect
R_AARCH64_RELATIVE.
For MIPS, the (if SymbolRel, then RelativeRel) code is to keep its
behavior unchanged.
Note, in ppc64-abs64-dyn.s, R_PPC64_TOC gets an incorrect addend because
computeAddend() doesn't compute the correct address. We seem to have the
wrong behavior for a long time. The important thing seems that a dynamic
relocation R_PPC64_TOC should not be created as the dynamic loader will
error R_PPC64_TOC is not supported.
Reviewers: atanasyan, grimar, peter.smith, ruiu, sfertile, espindola
Reviewed By: ruiu
Differential Revision: https://reviews.llvm.org/D63383
llvm-svn: 363928
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions