mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-08-01 02:29:19 +00:00
f7d5278fb3
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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@116823 91177308-0d34-0410-b5e6-96231b3b80d8
32 lines
1.0 KiB
ArmAsm
32 lines
1.0 KiB
ArmAsm
// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - | elf-dump --dump-section-data | FileCheck %s
|
|
|
|
// Test that relocations with local symbols are represented as relocations
|
|
// with the section. They should be equivalent, but gas behaves like this.
|
|
|
|
movl foo, %r14d
|
|
foo:
|
|
|
|
// Section number 1 is .text
|
|
// CHECK: # Section 0x00000001
|
|
// CHECK-next: (('sh_name', 0x00000001) # '.text'
|
|
|
|
// Symbol number 2 is section number 1
|
|
// CHECK: # Symbol 0x00000002
|
|
// CHECK-NEXT: (('st_name', 0x00000000) # ''
|
|
// CHECK-NEXT: ('st_bind', 0x00000000)
|
|
// CHECK-NEXT: ('st_type', 0x00000003)
|
|
// CHECK-NEXT: ('st_other', 0x00000000)
|
|
// CHECK-NEXT: ('st_shndx', 0x00000001)
|
|
// CHECK-NEXT: ('st_value', 0x00000000)
|
|
// CHECK-NEXT: ('st_size', 0x00000000)
|
|
|
|
// Relocation refers to symbol number 2
|
|
// CHECK: ('_relocations', [
|
|
// CHECK-NEXT: # Relocation 0x00000000
|
|
// CHECK-NEXT: (('r_offset',
|
|
// CHECK-NEXT: ('r_sym', 0x00000002)
|
|
// CHECK-NEXT: ('r_type',
|
|
// CHECK-NEXT: ('r_addend',
|
|
// CHECK-NEXT: ),
|
|
// CHECK-NEXT: ])
|