blob: 5de23853dcd2bf943b5c111f7d17259fc488a761 [file] [log] [blame]
// REQUIRES: arm
// RUN: llvm-mc -filetype=obj -triple=armv7a-none-linux-gnueabi %s -o %t.o
// RUN: ld.lld %t.o -o %t
// RUN: llvm-objdump -s --triple=armv7a-none-linux-gnueabi %t | FileCheck %s
// RUN: ld.lld %t.o --target2=got-rel -o %t2
// RUN: llvm-objdump -s --triple=armv7a-none-linux-gnueabi %t2 | FileCheck %s
// RUN: ld.lld %t.o --target2=abs -o %t3
// RUN: llvm-objdump -s --triple=armv7a-none-linux-gnueabi %t3 | FileCheck --check-prefix=CHECK-ABS %s
// RUN: ld.lld %t.o --target2=rel -o %t4
// RUN: llvm-objdump -s --triple=armv7a-none-linux-gnueabi %t4 | FileCheck --check-prefix=CHECK-REL %s
// The R_ARM_TARGET2 is present in .ARM.extab sections. It can be handled as
// either R_ARM_ABS32, R_ARM_REL32 or R_ARM_GOT_PREL. For ARM linux the default
// is R_ARM_GOT_PREL. The other two options are primarily used for bare-metal,
// they can be selected with the --target2=abs or --target2=rel option.
.syntax unified
.text
.globl _start
.align 2
_start:
.type function, %function
.fnstart
bx lr
.personality __gxx_personality_v0
.handlerdata
.word _ZTIi(TARGET2)
.text
.fnend
.global __gxx_personality_v0
.type function, %function
__gxx_personality_v0:
bx lr
.rodata
_ZTIi: .word 0
// CHECK: Contents of section .ARM.extab:
// 0x1012c + 0x2010 = 0x1213c = .got
// CHECK-NEXT: 10124 14000100 b0b0b000 10000200
// CHECK-ABS: Contents of section .ARM.extab:
// 0x100f0 = .rodata
// CHECK-ABS-NEXT: 100e4 14000100 b0b0b000 f0000100
// CHECK-REL: Contents of section .ARM.extab:
// 0x100ec + 4 = 0x100f0 = .rodata
// CHECK-REL-NEXT: 100e4 14000100 b0b0b000 04000000
// CHECK: Contents of section .rodata:
// CHECK-NEXT: 10130 00000000
// CHECK-ABS: Contents of section .rodata:
// CHECK-ABS-NEXT: 100f0 00000000
// CHECK-REL: Contents of section .rodata:
// CHECK-REL-NEXT: 100f0 00000000
// CHECK: Contents of section .got:
// 10130 = _ZTIi
// CHECK-NEXT: 3013c 30010100