llvm-project/lld/test/ELF/aarch64-cortex-a53-843419-l...

// REQUIRES: aarch64
// RUN: llvm-mc -filetype=obj -triple=aarch64-none-linux %s -o %t.o
// RUN: ld.lld --fix-cortex-a53-843419 -Ttext=0x8000000 %t.o -o %t2
// RUN: llvm-objdump -d --start-address=0x8001000 --stop-address=0x8001004 %t2 | FileCheck %s

.section .text.01, "ax", %progbits
.balign 4096
.space 4096 - 8
adrp x0, thunk
ldr x1, [x1, #0]
// CHECK: <thunk>:
// CHECK-NEXT: b 0xc001008 <__CortexA53843419_8001000>
thunk:
ldr x0, [x0, :got_lo12:thunk]
ret
.space 64 * 1024 * 1024

.section .text.02, "ax", %progbits
.space 64 * 1024 * 1024
ELF: AArch64: Fix errata patch address calculation. The code here wants the output section offset of the instruction requiring the errata patch, not the virtual address. Without this change we can end up placing a patch out of range if the virtual address of the code section is large enough. Differential Revision: https://reviews.llvm.org/D55732 llvm-svn: 349386 2018-12-18 04:15:12 +08:00			`// REQUIRES: aarch64`
			`// RUN: llvm-mc -filetype=obj -triple=aarch64-none-linux %s -o %t.o`
			`// RUN: ld.lld --fix-cortex-a53-843419 -Ttext=0x8000000 %t.o -o %t2`
			`// RUN: llvm-objdump -d --start-address=0x8001000 --stop-address=0x8001004 %t2 \| FileCheck %s`

			`.section .text.01, "ax", %progbits`
			`.balign 4096`
			`.space 4096 - 8`
			`adrp x0, thunk`
			`ldr x1, [x1, #0]`
[llvm-objdump] -d: print `00000000 <foo>:` instead of `00000000 foo:` The new behavior matches GNU objdump. A pair of angle brackets makes tests slightly easier. `.foo:` is not unique and thus cannot be used in a `CHECK-LABEL:` directive. Without `-LABEL`, the CHECK line can match the `Disassembly of section` line and causes the next `CHECK-NEXT:` to fail. ``` Disassembly of section .foo: 0000000000001634 .foo: ``` Bdragon: <> has metalinguistic connotation. it just "feels right" Reviewed By: rupprecht Differential Revision: https://reviews.llvm.org/D75713 2020-03-06 06:18:38 +08:00			`// CHECK: <thunk>:`
[AArch64InstPrinter] Change printAlignedLabel to print the target address in hexadecimal form Similar to D76580 (x86) and D76591 (PPC). ``` // llvm-objdump -d output (before) 10000: 08 00 00 94 bl #32 10004: 08 00 00 94 bl #32 // llvm-objdump -d output (after) 10000: 08 00 00 94 bl 0x10020 10004: 08 00 00 94 bl 0x10024 // GNU objdump -d. The lack of 0x is not ideal due to ambiguity. 10000: 94000008 bl 10020 <bar+0x18> 10004: 94000008 bl 10024 <bar+0x1c> ``` The new output makes it easier to find the jump target. Differential Revision: https://reviews.llvm.org/D77853 2020-04-10 09:46:35 +08:00			`// CHECK-NEXT: b 0xc001008 <__CortexA53843419_8001000>`
ELF: AArch64: Fix errata patch address calculation. The code here wants the output section offset of the instruction requiring the errata patch, not the virtual address. Without this change we can end up placing a patch out of range if the virtual address of the code section is large enough. Differential Revision: https://reviews.llvm.org/D55732 llvm-svn: 349386 2018-12-18 04:15:12 +08:00			`thunk:`
			`ldr x0, [x0, :got_lo12:thunk]`
			`ret`
			`.space 64 * 1024 * 1024`

			`.section .text.02, "ax", %progbits`
			`.space 64 * 1024 * 1024`