[ARM] Better OR's for MVE compares
[llvm-core.git] / test / MC / ELF / debug-line.s
blob89f07803f4b9ab1f5bd9288b3b6f82ad20352ad2
1 // RUN: llvm-mc -filetype=obj -triple x86_64-pc-linux-gnu %s -o - | llvm-readobj -S --sd | FileCheck %s
3 // Test that .debug_line is populated. TODO: This test should really be using
4 // llvm-dwarfdump, but it cannot parse this particular object file. The content
5 // of .debug_line was checked using GNU binutils:
7 // $ objdump --dwarf=decodedline debug-line.o
8 // [...]
9 // File name Line number Starting address
10 // foo.c 4 0
11 // foo.c 5 0x4
12 // foo.c 6 0x5
14 // CHECK: Section {
15 // CHECK: Name: .debug_line
16 // CHECK-NEXT: Type: SHT_PROGBITS
17 // CHECK-NEXT: Flags [
18 // CHECK-NEXT: ]
19 // CHECK-NEXT: Address: 0x0
20 // CHECK-NEXT: Offset:
21 // CHECK-NEXT: Size: 58
22 // CHECK-NEXT: Link: 0
23 // CHECK-NEXT: Info: 0
24 // CHECK-NEXT: AddressAlignment: 1
25 // CHECK-NEXT: EntrySize: 0
26 // CHECK-NEXT: SectionData (
28 // CHECK-NEXT: 0000: 36000000 04001D00 00000101 01FB0E0D
29 // CHECK-NEXT: 0010: 00010101 01000000 01000001 00666F6F
30 // CHECK-NEXT: 0020: 2E630000 00000000 09020000 00000000
31 // CHECK-NEXT: 0030: 0000154B 21020800 0101
32 // CHECK-NEXT: )
33 // CHECK-NEXT: }
35 .section .debug_line,"",@progbits
36 .text
38 .file 1 "foo.c"
39 .loc 1 4 0
40 subq $8, %rsp
42 // Test that .loc works with values, not just instructions.
44 .loc 1 5 0
45 .byte 0xc3
47 .loc 1 6 0
49 .quad l