old-cross-binutils/ld/testsuite/ld-aarch64/rela-abs-relative-be.d

#name: rela-abs-relative (big endian)
#source: rela-abs-relative.s
#ld: -shared -Ttext-segment=0x100000 -Tdata=0x200000 -Trelocs.ld
#target: aarch64_be-*-*
#objdump: -dR -j .data
#...

Disassembly of section .data:

.* <a>:
  200000:	00 00 00 00 ca fe ca fe 00 00 00 00 00 01 00 ca.*
			200008: R_AARCH64_RELATIVE	\*ABS\*\+0x100ca
  200010:	00 00 00 00 de ad de ad.*
[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. 2016-05-03 10:59:37 +00:00			`#name: rela-abs-relative (big endian)`
			`#source: rela-abs-relative.s`
			`#ld: -shared -Ttext-segment=0x100000 -Tdata=0x200000 -Trelocs.ld`
			`#target: aarch64_be--`
			`#objdump: -dR -j .data`
			`#...`

			`Disassembly of section .data:`

			`.* <a>:`
			`200000: 00 00 00 00 ca fe ca fe 00 00 00 00 00 01 00 ca.*`
			`200008: R_AARCH64_RELATIVE \ABS\\+0x100ca`
			`200010: 00 00 00 00 de ad de ad.*`