llvm-mirror/test/MC/ELF/align-text.s

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

// Test that the .text directive doesn't cause alignment.

        .zero 1
        .text
        .zero 1

// CHECK:      (('sh_name', 0x00000001) # '.text'
// CHECK-NEXT:  ('sh_type', 0x00000001)
// CHECK-NEXT:  ('sh_flags', 0x0000000000000006)
// CHECK-NEXT:   ('sh_addr', 0x0000000000000000)
// CHECK-NEXT:   ('sh_offset', 0x0000000000000040)
// CHECK-NEXT:   ('sh_size', 0x0000000000000002)
// CHECK-NEXT:   ('sh_link', 0x00000000)
// CHECK-NEXT:   ('sh_info', 0x00000000)
// CHECK-NEXT:   ('sh_addralign', 0x0000000000000004)
// CHECK-NEXT:   ('sh_entsize', 0x0000000000000000)
// CHECK-NEXT:  ),
Make sure .text doesn't produce extra alignment. llvm-svn: 114895 2010-09-27 23:40:27 +02:00			`// RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - \| elf-dump \| FileCheck %s`

			`// Test that the .text directive doesn't cause alignment.`

			`.zero 1`
			`.text`
			`.zero 1`

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: (('sh_name', 0x00000001) # '.text'`
			`// CHECK-NEXT: ('sh_type', 0x00000001)`
Fix the bitwidth of the remaining fields. llvm-svn: 136884 2011-08-04 19:00:11 +02:00			`// CHECK-NEXT: ('sh_flags', 0x0000000000000006)`
			`// CHECK-NEXT: ('sh_addr', 0x0000000000000000)`
			`// CHECK-NEXT: ('sh_offset', 0x0000000000000040)`
			`// CHECK-NEXT: ('sh_size', 0x0000000000000002)`
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: ('sh_link', 0x00000000)`
			`// CHECK-NEXT: ('sh_info', 0x00000000)`
Fix the bitwidth of the remaining fields. llvm-svn: 136884 2011-08-04 19:00:11 +02:00			`// CHECK-NEXT: ('sh_addralign', 0x0000000000000004)`
			`// CHECK-NEXT: ('sh_entsize', 0x0000000000000000)`
Make sure .text doesn't produce extra alignment. llvm-svn: 114895 2010-09-27 23:40:27 +02:00			`// CHECK-NEXT: ),`