llvm-project/llvm/test/MC/ELF/plt.s

// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - | elf-dump  | FileCheck %s

// Test that this produces a R_X86_64_PLT32.

	jmp	foo@PLT

// CHECK:      ('_relocations', [
// CHECK-NEXT:   # Relocation 0
// CHECK-NEXT:    (('r_offset',
// CHECK-NEXT:     ('r_sym',
// CHECK-NEXT:     ('r_type', 0x00000004)
// CHECK-NEXT:     ('r_addend',
// CHECK-NEXT:    ),
// CHECK-NEXT:   ])
Produce a R_X86_64_PLT32 when needed. llvm-svn: 115541 2010-10-05 03:04:13 +08:00			`// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - \| elf-dump \| FileCheck %s`

			`// Test that this produces a R_X86_64_PLT32.`

			`jmp foo@PLT`

			`// CHECK: ('_relocations', [`
Change anther counter to decimal. llvm-svn: 136870 2011-08-04 22:01:03 +08:00			`// CHECK-NEXT: # Relocation 0`
Produce a R_X86_64_PLT32 when needed. llvm-svn: 115541 2010-10-05 03:04:13 +08:00			`// CHECK-NEXT: (('r_offset',`
			`// CHECK-NEXT: ('r_sym',`
Fixing r116753 r116756 r116777 The failures in r116753 r116756 were caused by a python issue - Python likes to append 'L' suffix to stringified numbers if the number is larger than a machine int. Unfortunately, this causes a divergence of behavior between 32 and 64 bit python versions. I re-crafted elf-dump/common_dump to take care of these issues by: 1. always printing 0x (makes for easy sed/regex) 2. always print fixed length (exactly 2 + numBits/4 digits long) by mod ((2^numBits) - 1) 3. left-padded with '0' There is a residual common routine that is also used by macho-dump (dataToHex) , so I left the 'section_data' test values alone. llvm-svn: 116823 2010-10-20 01:39:10 +08:00			`// CHECK-NEXT: ('r_type', 0x00000004)`
Produce a R_X86_64_PLT32 when needed. llvm-svn: 115541 2010-10-05 03:04:13 +08:00			`// CHECK-NEXT: ('r_addend',`
			`// CHECK-NEXT: ),`
			`// CHECK-NEXT: ])`