content (full) in projects: llvm-project

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:content (Results 1 – 25 of 1678) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...68

/llvm-project/llvm/test/tools/obj2yaml/ELF/
H A D	hash-section.yaml	`4 ## a SHT_HASH section when it has content of a correct size. 28 Content: '0100000002000000030000000400000005000000' 32 Content: '0000000000000000' 34 ## Check that obj2yaml falls back to using the "Content" tag when 38 # RUN: obj2yaml %t2 \| FileCheck %s --check-prefix=CONTENT 40 # CONTENT: - Name: .empty_hash 41 # CONTENT-NEXT: Type: SHT_HASH 42 # CONTENT-NEXT: Content: '' 43 # CONTENT-NEXT: - Name: .invalid_header 44 # CONTENT-NEXT: Type: SHT_HASH [all …]`
/llvm-project/llvm/test/tools/yaml2obj/ELF/
H A D	reloc-sec.yaml	1 ## Check how "Content", "Size" and "Entries" keys can be used to 2 ## describe a content for relocations sections. 4 ## Check we can use the "Content" key with the "Size" key when the size is greater 5 ## than or equal to the content size. 8 # RUN: FileCheck %s --check-prefix=CONTENT-SIZE-ERR 10 # CONTENT-SIZE-ERR: error: Section size must be greater than or equal to the content size 24 Content: [[CONTENT=<none>]] 29 # RUN: FileCheck %s --check-prefix=CHECK-CONTENT -DDATA="0011" 33 # RUN: FileCheck %s --check-prefix=CHECK-CONTENT -DDATA="001100" 35 # CHECK-CONTENT: Name: .rela [all …]
H A D	group.yaml	1 ## Check how the "Content", "Size" and "Members" keys can be used to 2 ## describe the content for group sections. 4 ## Check we can use the "Content" key with the "Size" key when the size is greater 5 ## than or equal to the content size. 8 # RUN: FileCheck %s --check-prefix=CONTENT-SIZE-ERR 10 # CONTENT-SIZE-ERR: error: Section size must be greater than or equal to the content size 24 Content: [[CONTENT=<none>]] 29 # RUN: FileCheck %s --check-prefix=CHECK-CONTENT -DDATA="0011" 33 # RUN: FileCheck %s --check-prefix=CHECK-CONTENT -DDATA="001100" 35 # CHECK-CONTENT: Name: .group [all …]
H A D	hash-section.yaml	`3 ## Check we can describe a SHT_HASH section using the "Content" tag. 8 # RUN: FileCheck %s -DENTSIZE=4 --check-prefix=CONTENT 10 # CONTENT: Name: .hash 11 # CONTENT-NEXT: Type: SHT_HASH 12 # CONTENT-NEXT: Flags [ 13 # CONTENT-NEXT: ] 14 # CONTENT-NEXT: Address: 0x0 15 # CONTENT-NEXT: Offset: 0x44 16 # CONTENT-NEXT: Size: 20 17 # CONTENT-NEXT: Link: 1 [all …]`
H A D	call-graph-profile-section.yaml	3 ## Test that the content of SHT_LLVM_CALL_GRAPH_PROFILE sections 61 ## Check we can specify none of "Content", "Entries", and "Size" tags. 84 ## Check we can describe SHT_LLVM_CALL_GRAPH_PROFILE sections using the "Content" tag. 85 # RUN: yaml2obj --docnum=3 %s -o %t.content 86 # RUN: llvm-readobj --sections --section-data %t.content \| FileCheck %s --check-prefix=CONTENT 88 # CONTENT: Name: .llvm.call-graph-profile 89 # CONTENT: SectionData ( 90 # CONTENT-NEXT: 0000: 11223344 \| 91 # CONTENT-NEXT: ) 101 Content: "11223344" [all …]
H A D	gnu-hash-section.yaml	`3 ## Check we can describe a SHT_GNU_HASH section using the "Content" tag. 7 # RUN: llvm-readobj --sections --section-data %t1 \| FileCheck %s --check-prefix=CONTENT 9 # CONTENT: Name: .gnu.hash 10 # CONTENT-NEXT: Type: SHT_GNU_HASH 11 # CONTENT-NEXT: Flags [ 12 # CONTENT-NEXT: ] 13 # CONTENT-NEXT: Address: 0x0 14 # CONTENT-NEXT: Offset: 0x40 15 # CONTENT-NEXT: Size: 3 16 # CONTENT-NEXT: Link: 2 [all …]`
H A D	llvm-addrsig-section.yaml	`99 ## Check we can use the "Content" tag to specify any data for SHT_LLVM_ADDRSIG sections. 102 # RUN: llvm-readobj --sections --section-data %t5 \| FileCheck %s --check-prefix=CONTENT 104 # CONTENT: Type: SHT_LLVM_ADDRSIG 105 # CONTENT: Size: 106 # CONTENT-SAME: 5 107 # CONTENT: SectionData ( 108 # CONTENT-NEXT: 0000: 11223344 55 109 # CONTENT-NEXT: ) 119 Content: "1122334455" 121 ## Check we emit an empty section if neither "Content", "Size" nor "Symbols" were set. [all …]`
H A D	verdef-section.yaml	`120 ## Check we can use "Content" to describe the content. 124 # RUN: llvm-readobj --sections --section-data %t2 \| FileCheck %s --check-prefix=CONTENT 126 # CONTENT: Name: .gnu.version_d 127 # CONTENT-NEXT: Type: SHT_GNU_verdef 128 # CONTENT-NEXT: Flags [ (0x2) 129 # CONTENT-NEXT: SHF_ALLOC (0x2) 130 # CONTENT-NEXT: ] 131 # CONTENT-NEXT: Address: 0x0 132 # CONTENT-NEXT: Offset: 0x40 133 # CONTENT-NEXT: Size: 3 [all …]`
H A D	relr-section.yaml	3 ## Test that the content of SHT_RELR sections for 64-bit little endian targets is correct. 24 ## Test that the content of SHT_RELR sections for 64-bit big endian targets is correct. 47 ## Test that the content of SHT_RELR sections for 32-bit little endian targets is correct. 67 ## Test that the content of SHT_RELR sections for 32-bit big endian targets is correct. 105 Content: "12" 139 ## Check we can use the "Content" key with the "Size" key when the size is greater 140 ## than or equal to the content size. 143 # RUN: FileCheck %s --check-prefix=CONTENT-SIZE-ERR 145 # CONTENT-SIZE-ERR: error: Section size must be greater than or equal to the content size 157 Content: [[CONTENT=<none>]] [all …]
H A D	note-section.yaml	55 ## Check that for 32-bit little-endian case we produce the same section content. 78 ## Check they produce the same content. 155 ## Check we can use the "Content" tag to specify any data for SHT_NOTE sections. 158 # RUN: llvm-readobj --sections --section-data %t7 \| FileCheck %s --check-prefix=CONTENT 160 # CONTENT: Name: .note.foo 161 # CONTENT: SectionData ( 162 # CONTENT-NEXT: 0000: 11223344 55 \| 163 # CONTENT-NEXT: ) 173 Content: "1122334455" 175 ## Check we emit an empty section if neither "Content", "Siz [all...]
H A D	versym-section.yaml	116 ## Check we can use the "Content" key with the "Size" key when the size is greater 117 ## than or equal to the content size. 121 # RUN: FileCheck %s --check-prefix=CONTENT-SIZE-ERR 123 # CONTENT-SIZE-ERR: error: Section size must be greater than or equal to the content size 134 Content: [[CONTENT=<none>]] 139 # RUN: FileCheck %s --check-prefix=CHECK-CONTENT -DDATA="0011" 143 # RUN: FileCheck %s --check-prefix=CHECK-CONTENT -DDATA="001100" 145 # CHECK-CONTENT: Name: .gnu.version 146 # CHECK-CONTENT-NEXT: Type: SHT_GNU_versym (0x6FFFFFFF) 147 # CHECK-CONTENT-NEXT: Flags [ (0x0) [all …]
H A D	arm-exidx-section.yaml	3 ## Test that the content of SHT_ARM_EXIDX sections, 53 ## Also check that we are able to specify none of "Entries", "Content" nor "Size" keys. 76 ## Check we can't use the "Entries" key together with the "Content" or "Size" keys. 83 # ENTRIES-ERR: error: "Entries" cannot be used with "Content" or "Size" 95 Content: [[CONTENT=<none>]] 98 ## Check we can use the "Content" key with the "Size" key when the size is greater 99 ## than or equal to the content size. 102 # RUN: FileCheck %s --check-prefix=CONTENT-SIZE-ERR 104 # CONTENT-SIZE-ERR: error: Section size must be greater than or equal to the content size 108 # RUN: FileCheck %s --check-prefix=CHECK-CONTENT -DDATA="00" [all …]
H A D	stack-sizes.yaml	`3 ## Test the following cases when the .stack_sizes Content field is specified: 5 ## a valid section content. 7 ## a broken (truncated) section content. 9 ## empty section content. 14 ## Case 1: valid content. 33 ## Case 2: truncated content. 40 ## Case 3: empty content. 54 Content: "100000000000000020" 58 Content: "1000000000000000" 62 Content: "" [all …]`
H A D	llvm-deplibs-section.yaml	4 ## "Libraries", "Size" and "Content" properies. 24 # LIBRARIES: Name: .deplibs.content 63 - Name: .deplibs.content 65 Content: "112233" 70 ## Check we report an error when "Libraries" and "Content"/"Size" keys are used together. 75 # LIBS-ERR: error: "Libraries" cannot be used with "Content" or "Size" 85 Content: [[CONTENT=<none>]] 89 ## Check we create an empty section when none of "Libraries", "Size" or "Content" are specified. 97 ## Check we can use the "Content" key with the "Size" key when the size is greater 98 ## than or equal to the content size. [all …]
H A D	dynamic-section-raw-content.yaml	1 ## Check how "Content", "Size" and "Entries" keys can be used to 2 ## describe a content for relocations sections. 4 ## Check we can use the "Content" key alone. 6 # RUN: yaml2obj -DCONTENT="01234567" %s -o %t1.content 7 # RUN: llvm-readobj --sections --section-data %t1.content \| \ 26 Content: [[CONTENT=<none>]] 36 ## Check we can use the "Content" key with the "Size" key when the size is greater 37 ## than or equal to the content size. 40 # RUN: FileCheck %s --check-prefix=CONTENT-SIZE-ERR 42 # CONTENT-SIZE-ERR: error: Section size must be greater than or equal to the content size [all …]
H A D	linker-options.yaml	4 ## Check we can use "Options", "Size" and "Content" alone to describe the data. 55 Content: "00112233" 90 ## Check we can't use "Options" or "Size" keys together with the "Content" key. 98 # TOGETHER: error: "Options" cannot be used with "Content" or "Size" 109 Content: [[CONTENT=<none>]] 112 ## Check we can omit "Options", "Content" and "Size" keys. This produces an empty section. 120 ## Check we can use the "Content" key with the "Size" key when the size is greater 121 ## than or equal to the content size. 124 # RUN: FileCheck %s --check-prefix=CONTENT-SIZE-ERR 126 # CONTENT-SIZE-ERR: error: Section size must be greater than or equal to the content size [all …]
/llvm-project/llvm/test/tools/llvm-objcopy/ELF/
H A D	preserve-segment-contents.test	`71 Content: 'abbababa' 77 Content: '11223344' 80 Content: 'abbababa' 88 Content: 'abbababa' 92 Content: '55667788' 96 Content: 'abbababa' 100 Content: '9900aabb' 105 Content: 'abbababa' 110 Content: 'ccddeeff' 113 Content: 'fefefefe' [all …]`
/llvm-project/lldb/test/Shell/ObjectFile/ELF/
H A D	build-id-case.yaml	`40 Content: 040000001400000003000000474E55001B8A73AC238390E32A7FF4AC8EBE4D6A41ECF5C9 46 Content: DEADBEEFBAADF00D 49 Content: DEADBEEFBAADF00D 52 Content: DEADBEEFBAADF00D 55 Content: DEADBEEFBAADF00D 58 Content: DEADBEEFBAADF00D 61 Content: DEADBEEFBAADF00D 64 Content: DEADBEEFBAADF00D 67 Content: DEADBEEFBAADF00D 70 Content: DEADBEEFBAADF00D [all …]`
H A D	section-types.yaml	`72 Content: DEADBEEFBAADF00D 76 Content: DEADBEEFBAADF00D 80 Content: DEADBEEFBAADF00D 84 Content: DEADBEEFBAADF00D 88 Content: DEADBEEFBAADF00D 92 Content: DEADBEEFBAADF00D 96 Content: DEADBEEFBAADF00D 100 Content: DEADBEEFBAADF00D 104 Content: DEADBEEFBAADF00D 108 Content: DEADBEEFBAADF00D [all …]`
/llvm-project/lldb/test/Shell/Breakpoint/Inputs/
H A D	single-file-split-dwarf.o.yaml	12 Content: 554889E531C0C745FC000000005DC390554889E55DC3 16 Content: 0C000000050000000000000000000000 21 …Content: 746573742E6F002F686F6D652F756D622F74657374735F323031382F39355F6C6C64622F726570726… 26 Content: '' 30 Content: 01110010177217B042251B25B44219B3421711011206000000 34 …Content: 2B00000005000408000000003F4B7684A29835B901000000000000000000010000000000000000000… 38 Content: '00' 43 Content: 200000000500000000000000070000002A00000033000000380000003C00000044000000 48 …Content: 746573742E6F00636C616E672076657273696F6E20382E302E3020287472756E6B203334323731382… 53 …Content: 3600000005000508000000003F4B7684A29835B901000104000202000F00000001560301013500000… [all …]
H A D	split-dwarf5-debug-stroffsets-main.yaml	14 …Content: 31ED4989D15E4889E24883E4F0505449C7C0C008400048C7C15008400048C7C790074000E877FFFFF… 20 …Content: 011B033BE8FDFFFF0C000000A4FAFFFF04FFFFFF14FBFFFF44FFFFFFF4FBFFFF04FEFFFF04FCFFFF7… 24 Content: 0C00000005000000000000000A0000000C000000050000008F0000000A000000 29 …Content: 66696C65312E64776F000000000000000000000000000000000000000000000000000000000000000… 33 …Content: 01110010177217B042251B25B44219731711015523741700000001110010177217B042251B25B4421… 37 …Content: 2C00000005000408000000008D03E0CB5B41F18901000000000800000000010800000000000000000… 41 …Content: 1C00000005000800010000000400000003000B03013203020603030903046E0013000000050008000… 45 Content: '0000' 49 …Content: 2C0000000500080010074000000000002007400000000000700740000000000080074000000000009… 53 …Content: 84010000050000000100000000000000000000000D0000000D00000013000000080000004C4C564D3… [all …]
H A D	single-file-split-dwarf.yaml	14 …Content: 31ED4989D15E4889E24883E4F0505449C7C0B005400048C7C14005400048C7C720054000E8B7FFFFF… 18 Content: 0C000000050000000000000007000000 23 …Content: 746573742E6F000000000000000000000000000000000000000000000000000000000000000000000… 27 Content: 01110010177217B042251B25B44219B3421711011206000000 31 …Content: 2B00000005000408000000003F4B7684A29835B901000000000800000000010800000020054000000… 35 Content: '00' 39 Content: '140000000500080020054000000000003005400000000000' 43 …Content: A00000000500000001000000000000000000000004000000040000000D000000080000004C4C564D3… 47 Content: 210000000200000000002F0000002900000030666F6F001A000000306D61696E0000000000 51 Content: 170000000200000000002F0000003500000090696E740000000000 [all …]
H A D	split-dwarf-5-addrbase.yaml	14 …Content: 31ED4989D15E4889E24883E4F0505449C7C0C005400048C7C15005400048C7C730054000E8B7FFFFF… 18 Content: 0C000000050000000000000009000000 23 …Content: 746573742E64776F002F686F6D652F756D622F74657374735F323031382F3132322F69737375652F6… 27 Content: 01110010177217B042251B25B442197317111B1206000000 31 … Content: 240000000500040800000000E93484C441B7E84A010000000008000000000108000000002C000000 35 Content: '00' 39 Content: '140000000500080020054000000000003005400000000000' 43 …Content: A00000000500000001000000000000000000000004000000040000000D000000080000004C4C564D3… 47 Content: 210000000200000000002800000026000000306D61696E001A0000003062617A0000000000 51 Content: '17000000020000000000280000003500000090696E740000000000' [all …]
/llvm-project/clang-tools-extra/clangd/test/
H A D	protocol.test	`9 Content-Length: 125 10 Content-Type: application/vscode-jsonrpc; charset-utf-8 13 # Test message with Content-Type after Content-Length 18 Content-Length: 246 22 Content-Length: 104 26 Content-Type: application/vscode-jsonrpc; charset-utf-8 27 Content-Length: 146 30 # Test message with Content-Type before Content-Length 48 Content-Type: application/vscode-jsonrpc; charset-utf-8 49 Content-Length: 146 [all …]`
/llvm-project/llvm/test/tools/obj2yaml/MachO/
H A D	debug-aranges.yaml	2 ## The content of the __debug_aranges section should be written in 3 ## the "DWARF" entry and the "content" field should remain empty. 80 ## This makes the DWARF parser fail to parse it and we will dump it as a raw content section. 82 # RUN: yaml2obj --docnum=1 -DLENGTH=0x2 %s \| obj2yaml \| FileCheck %s --check-prefix=RAW-CONTENT 84 # RAW-CONTENT: - sectname: __debug_aranges 85 # RAW-CONTENT-NEXT: segname: __DWARF 86 # RAW-CONTENT-NEXT: addr: 0x0 87 # RAW-CONTENT-NEXT: size: 64 88 # RAW-CONTENT-NEXT: offset: 0x210 89 # RAW-CONTENT-NEXT: align: 0 [all …]

12 3 4 5 6 7 8 9 10 >>...68