llvm-mirror/test/MC/ELF/file.s

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

// Test that the STT_FILE symbol precedes the other local symbols.

.file "foo"
foa:
// CHECK:    # Symbol 0x00000001
// CHECK-NEXT:    (('st_name', 0x00000001) # 'foo'
// CHECK-NEXT:     ('st_bind', 0x00000000)
// CHECK-NEXT:     ('st_type', 0x00000004)
// CHECK-NEXT:     ('st_other', 0x00000000)
// CHECK-NEXT:     ('st_shndx', 0x0000fff1)
// CHECK-NEXT:     ('st_value', 0x0000000000000000)
// CHECK-NEXT:     ('st_size', 0x0000000000000000)
// CHECK-NEXT:    ),
// CHECK-NEXT:    # Symbol 0x00000002
// CHECK-NEXT:    (('st_name', 0x00000005) # 'foa'
// CHECK-NEXT:     ('st_bind', 0x00000000)
// CHECK-NEXT:     ('st_type', 0x00000000)
// CHECK-NEXT:     ('st_other', 0x00000000)
// CHECK-NEXT:     ('st_shndx', 0x00000001)
// CHECK-NEXT:     ('st_value', 0x0000000000000000)
// CHECK-NEXT:     ('st_size', 0x0000000000000000)
Make sure the STT_FILE symbol is the first one in the symbol table. llvm-svn: 114285 2010-09-18 17:03:21 +02:00			`// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - \| elf-dump \| FileCheck %s`

			`// Test that the STT_FILE symbol precedes the other local symbols.`

			`.file "foo"`
			`foa:`
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-19 19:39:10 +02:00			`// CHECK: # Symbol 0x00000001`
			`// CHECK-NEXT: (('st_name', 0x00000001) # 'foo'`
			`// CHECK-NEXT: ('st_bind', 0x00000000)`
			`// CHECK-NEXT: ('st_type', 0x00000004)`
			`// CHECK-NEXT: ('st_other', 0x00000000)`
			`// CHECK-NEXT: ('st_shndx', 0x0000fff1)`
Print all 64bits for st_value and st_size. Adjust tests accordingly. llvm-svn: 122263 2010-12-20 21:49:43 +01:00			`// CHECK-NEXT: ('st_value', 0x0000000000000000)`
			`// CHECK-NEXT: ('st_size', 0x0000000000000000)`
Make sure the STT_FILE symbol is the first one in the symbol table. llvm-svn: 114285 2010-09-18 17:03:21 +02:00			`// CHECK-NEXT: ),`
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-19 19:39:10 +02:00			`// CHECK-NEXT: # Symbol 0x00000002`
			`// CHECK-NEXT: (('st_name', 0x00000005) # 'foa'`
			`// CHECK-NEXT: ('st_bind', 0x00000000)`
			`// CHECK-NEXT: ('st_type', 0x00000000)`
			`// CHECK-NEXT: ('st_other', 0x00000000)`
			`// CHECK-NEXT: ('st_shndx', 0x00000001)`
Print all 64bits for st_value and st_size. Adjust tests accordingly. llvm-svn: 122263 2010-12-20 21:49:43 +01:00			`// CHECK-NEXT: ('st_value', 0x0000000000000000)`
			`// CHECK-NEXT: ('st_size', 0x0000000000000000)`