llvm-project/llvm/test/MC/AArch64/elf-reloc-addsubimm.s

// RUN: llvm-mc -triple=aarch64-none-linux-gnu -filetype=obj %s -o - | \
// RUN:   llvm-readobj -r | FileCheck -check-prefix=OBJ %s

        add x2, x3, #:lo12:some_label

// OBJ:      Relocations [
// OBJ-NEXT:   Section (2) .rela.text {
// OBJ-NEXT:     0x0 R_AARCH64_ADD_ABS_LO12_NC some_label 0x0
// OBJ-NEXT:   }
// OBJ-NEXT: ]
AArch64: use full triple for ELF tests These tests rely specifically on the names of ELF relocations, let alone any other detail. There's no way they'd work if LLVM was emitting something else by default. llvm-svn: 179376 2013-04-12 20:54:58 +08:00			`// RUN: llvm-mc -triple=aarch64-none-linux-gnu -filetype=obj %s -o - \| \`
Replace coff-/elf-dump with llvm-readobj llvm-svn: 179361 2013-04-12 12:06:46 +08:00			`// RUN: llvm-readobj -r \| FileCheck -check-prefix=OBJ %s`
Add AArch64 as an experimental target. This patch adds support for AArch64 (ARM's 64-bit architecture) to LLVM in the "experimental" category. Currently, it won't be built unless requested explicitly. This initial commit should have support for: + Assembly of all scalar (i.e. non-NEON, non-Crypto) instructions (except the late addition CRC instructions). + CodeGen features required for C++03 and C99. + Compilation for the "small" memory model: code+static data < 4GB. + Absolute and position-independent code. + GNU-style (i.e. "__thread") TLS. + Debugging information. The principal omission, currently, is performance tuning. This patch excludes the NEON support also reviewed due to an outbreak of batshit insanity in our legal department. That will be committed soon bringing the changes to precisely what has been approved. Further reviews would be gratefully received. llvm-svn: 174054 2013-01-31 20:12:40 +08:00
			`add x2, x3, #:lo12:some_label`

Replace coff-/elf-dump with llvm-readobj llvm-svn: 179361 2013-04-12 12:06:46 +08:00			`// OBJ: Relocations [`
Change how we iterate over relocations on ELF. For COFF and MachO, sections semantically have relocations that apply to them. That is not the case on ELF. In relocatable objects (.o), a section with relocations in ELF has offsets to another section where the relocations should be applied. In dynamic objects and executables, relocations don't have an offset, they have a virtual address. The section sh_info may or may not point to another section, but that is not actually used for resolving the relocations. This patch exposes that in the ObjectFile API. It has the following advantages: * Most (all?) clients can handle this more efficiently. They will normally walk all relocations, so doing an effort to iterate in a particular order doesn't save time. * llvm-readobj now prints relocations in the same way the native readelf does. * probably most important, relocations that don't point to any section are now visible. This is the case of relocations in the rela.dyn section. See the updated relocation-executable.test for example. llvm-svn: 182908 2013-05-30 11:05:14 +08:00			`// OBJ-NEXT: Section (2) .rela.text {`
Replace coff-/elf-dump with llvm-readobj llvm-svn: 179361 2013-04-12 12:06:46 +08:00			`// OBJ-NEXT: 0x0 R_AARCH64_ADD_ABS_LO12_NC some_label 0x0`
			`// OBJ-NEXT: }`
			`// OBJ-NEXT: ]`