1ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// RUN: llvm-mc -triple=aarch64-linux-gnu -filetype=obj -o - %s| llvm-readobj -r - | FileCheck %s 2ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover .text 3ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// These should produce an ADRP/ADD pair to calculate the address of 4ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// testfn. The important point is that LLVM shouldn't think it can deal with the 5ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// relocation on the ADRP itself (even though it knows everything about the 6ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// relative offsets of testfn and foo) because its value depends on where this 7ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// object file's .text section gets relocated in memory. 8ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover adrp x0, sym 9ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover adrp x0, :got:sym 10ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover adrp x0, :gottprel:sym 11ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover adrp x0, :tlsdesc:sym 12ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover 13ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover .global sym 14ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northoversym: 15ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// CHECK: R_AARCH64_ADR_PREL_PG_HI21 sym 16ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// CHECK: R_AARCH64_ADR_GOT_PAGE sym 17ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// CHECK: R_AARCH64_TLSIE_ADR_GOTTPREL_PAGE21 sym 18ccb06ae8f3ef0135d4bddf4f0f61f619c3ce3f1eTim Northover// CHECK: R_AARCH64_TLSDESC_ADR_PAGE sym 19