mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-23 11:13:28 +01:00
da953f13b9
This mostly entails adding relocations, however there are a couple of changes to existing relocations: 1. R_AARCH64_NONE is defined to be zero rather than 256 R_AARCH64_NONE has been defined to be zero for a long time elsewhere e.g. binutils and glibc since the submission of the AArch64 port in 2012 so this is required for compatibility. 2. R_AARCH64_TLSDESC_ADR_PAGE renamed to R_AARCH64_TLSDESC_ADR_PAGE21 I don't think there is any way for relocation names to leak out of LLVM so this should not break anything. Tested with check-all with no regressions. llvm-svn: 222821
19 lines
779 B
ArmAsm
19 lines
779 B
ArmAsm
// RUN: llvm-mc -triple=aarch64-linux-gnu -filetype=obj -o - %s| llvm-readobj -r - | FileCheck %s
|
|
.text
|
|
// These should produce an ADRP/ADD pair to calculate the address of
|
|
// testfn. The important point is that LLVM shouldn't think it can deal with the
|
|
// relocation on the ADRP itself (even though it knows everything about the
|
|
// relative offsets of testfn and foo) because its value depends on where this
|
|
// object file's .text section gets relocated in memory.
|
|
adrp x0, sym
|
|
adrp x0, :got:sym
|
|
adrp x0, :gottprel:sym
|
|
adrp x0, :tlsdesc:sym
|
|
|
|
.global sym
|
|
sym:
|
|
// CHECK: R_AARCH64_ADR_PREL_PG_HI21 sym
|
|
// CHECK: R_AARCH64_ADR_GOT_PAGE sym
|
|
// CHECK: R_AARCH64_TLSIE_ADR_GOTTPREL_PAGE21 sym
|
|
// CHECK: R_AARCH64_TLSDESC_ADR_PAGE21 sym
|