diff options
| author | Jiong Wang <jiong.wang@arm.com> | 2016-05-03 11:59:37 +0100 |
|---|---|---|
| committer | Jiong Wang <jiong.wang@arm.com> | 2016-05-03 11:59:37 +0100 |
| commit | 1f56df9d0d5ad89806c24e71f296576d82344613 (patch) | |
| tree | 5119f229d105a5dbb5a18c77cef5407d318a7fde /ld/NEWS | |
| parent | 20f55f3866ab70778d08fec2c09626cff9ed781d (diff) | |
| download | gdb-1f56df9d0d5ad89806c24e71f296576d82344613.zip gdb-1f56df9d0d5ad89806c24e71f296576d82344613.tar.gz gdb-1f56df9d0d5ad89806c24e71f296576d82344613.tar.bz2 | |
[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.
Diffstat (limited to 'ld/NEWS')
| -rw-r--r-- | ld/NEWS | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -11,6 +11,9 @@ * The NOCROSSREFSTO command was added to the linker script language. +* Add --no-apply-dynamic-relocs to the AArch64 linker to do not apply link-time + values for dynamic relocations. + Changes in 2.26: * Add --fix-stm32l4xx-629360 to the ARM linker to enable a link-time |