From 1f56df9d0d5ad89806c24e71f296576d82344613 Mon Sep 17 00:00:00 2001 From: Jiong Wang Date: Tue, 3 May 2016 11:59:37 +0100 Subject: [AArch64] Also puts value in place for R_AARCH64_RELATIVE When handling absolute relocations for global symbols bind within the shared object, AArch64 will generate one dynamic RELATIVE relocation, but won't apply the value for this absolution relocations at static linking stage. This is different from AArch64 gold linker and x86-64. This is not a bug as AArch64 is RELA, there is only guarantee that relocation addend is placed in the relocation entry. But some system softwares originally writen for x86-64 might assume AArch64 bfd linker gets the same behavior as x86-64, then they could take advantage of this buy skipping those RELATIVE dynamic relocations if the load address is the same as the static linking address. This patch makes AArch64 BFD linker applies absolution relocations at static linking stage for scenario described above. Meanwhile old AArch64 android loader has a bug (PR19163) which relies on current linker behavior as a workaround, so the same option --no-apply-dynamic-relocs added. --- ld/ld.texinfo | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'ld/ld.texinfo') diff --git a/ld/ld.texinfo b/ld/ld.texinfo index 7a2ed3a..bc16764 100644 --- a/ld/ld.texinfo +++ b/ld/ld.texinfo @@ -6848,6 +6848,11 @@ The @samp{--long-plt} option enables the use of 16 byte PLT entries which support up to 4Gb of code. The default is to use 12 byte PLT entries which only support 512Mb of code. +@kindex --no-apply-dynamic-relocs +@cindex AArch64 rela addend +The @samp{--no-apply-dynamic-relocs} option makes AArch64 linker do not apply +link-time values for dynamic relocations. + @ifclear GENERIC @lowersections @end ifclear -- cgit v1.1