llvm-6502/test/MC/ELF/section.s

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

// Test that these names are accepted.

.section	.note.GNU-stack,"",@progbits
.section	.note.GNU-,"",@progbits
.section	-.note.GNU,"",@progbits

// CHECK: ('sh_name', 0x00000012) # '.note.GNU-stack'
// CHECK: ('sh_name', 0x00000022) # '.note.GNU-'
// CHECK: ('sh_name', 0x0000002d) # '-.note.GNU'
Make sure that names like .note.GNU-stack are accepted as valid section names. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@114091 91177308-0d34-0410-b5e6-96231b3b80d8 2010-09-16 17:05:55 +00:00			`// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - \| elf-dump \| FileCheck %s`

			`// Test that these names are accepted.`

			`.section .note.GNU-stack,"",@progbits`
			`.section .note.GNU-,"",@progbits`
			`.section -.note.GNU,"",@progbits`

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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@116823 91177308-0d34-0410-b5e6-96231b3b80d8 2010-10-19 17:39:10 +00:00			`// CHECK: ('sh_name', 0x00000012) # '.note.GNU-stack'`
			`// CHECK: ('sh_name', 0x00000022) # '.note.GNU-'`
			`// CHECK: ('sh_name', 0x0000002d) # '-.note.GNU'`