maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Object/obj2yaml.test

493 lines
22 KiB
Plaintext
Raw Normal View History

Use std::list so that we have a stable iterator. I will try to avoid creating these std::strings, but for now this gets the tests passing with libc++. llvm-svn: 182405
2013-05-22 02:53:50 +08:00
RUN: obj2yaml %p/Inputs/trivial-object-test.coff-i386 | FileCheck %s --check-prefix COFF-I386
RUN: obj2yaml %p/Inputs/trivial-object-test.coff-x86-64 | FileCheck %s --check-prefix COFF-X86-64
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
RUN: obj2yaml %p/Inputs/trivial-object-test.elf-mipsel | FileCheck %s --check-prefix ELF-MIPSEL
RUN: obj2yaml %p/Inputs/trivial-object-test.elf-mips64el | FileCheck %s --check-prefix ELF-MIPS64EL
RUN: obj2yaml %p/Inputs/trivial-object-test.elf-x86-64 | FileCheck %s --check-prefix ELF-X86-64
[AVR] Add ELF constants to headers Also adds a 'trivial' ELF file. This was generated by assembling and linking a file with the symbol main which contains a single return instruction. llvm-svn: 251096
2015-10-23 14:05:55 +08:00
RUN: obj2yaml %p/Inputs/trivial-object-test.elf-avr | FileCheck %s --check-prefix ELF-AVR
[WebAssembly] Be consistent in generating trivial test input files For each checked-in wasm file, make sure the there is corresponding .ll file that can be used to regenerate it if needed. Add test/Object/Inputs/trivial-object-test.wasm to match other formats and add some new wasm tests in test/Object. Differential Revision: https://reviews.llvm.org/D35213 llvm-svn: 307585
2017-07-11 04:43:26 +08:00
RUN: obj2yaml %p/Inputs/trivial-object-test.wasm | FileCheck %s --check-prefix WASM
RUN: obj2yaml %p/Inputs/unwind-section.elf-x86-64 | FileCheck %s --check-prefix ELF-X86-64-UNWIND
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386: header:
COFF-I386-NEXT: Machine: IMAGE_FILE_MACHINE_I386
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386: sections:
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386-NEXT: - Name: .text
COFF-I386-NEXT: Characteristics: [ IMAGE_SCN_CNT_CODE, IMAGE_SCN_MEM_EXECUTE, IMAGE_SCN_MEM_READ ]
COFF-I386-NEXT: Alignment: 16
COFF-I386-NEXT: SectionData: 83EC0CC744240800000000C7042400000000E800000000E8000000008B44240883C40CC3
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386: Relocations:
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386-NEXT: - VirtualAddress: 14
Print symbol names in relocations when dumping COFF as YAML. llvm-svn: 183403
2013-06-06 21:06:17 +08:00
COFF-I386-NEXT: SymbolName: L_.str
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386-NEXT: Type: IMAGE_REL_I386_DIR32
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386: - VirtualAddress: 19
Print symbol names in relocations when dumping COFF as YAML. llvm-svn: 183403
2013-06-06 21:06:17 +08:00
COFF-I386-NEXT: SymbolName: _puts
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386-NEXT: Type: IMAGE_REL_I386_REL32
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386: - VirtualAddress: 24
Print symbol names in relocations when dumping COFF as YAML. llvm-svn: 183403
2013-06-06 21:06:17 +08:00
COFF-I386-NEXT: SymbolName: _SomeOtherFunction
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386-NEXT: Type: IMAGE_REL_I386_REL32
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386: - Name: .data
COFF-I386-NEXT: Characteristics: [ IMAGE_SCN_CNT_INITIALIZED_DATA, IMAGE_SCN_MEM_READ, IMAGE_SCN_MEM_WRITE ]
COFF-I386-NEXT: Alignment: 1
COFF-I386-NEXT: SectionData: 48656C6C6F20576F726C642100
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386: symbols:
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386-NEXT: - Name: .text
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386-NEXT: Value: 0
COFF-I386-NEXT: SectionNumber: 1
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-I386-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-I386-NEXT: StorageClass: IMAGE_SYM_CLASS_STATIC
Object: Provide a richer means of describing auxiliary symbols The current state of affairs has auxiliary symbols described as a big bag of bytes. This is less than satisfying, it detracts from the YAML file as being human readable. Instead, allow for symbols to optionally contain their auxiliary data. This allows us to have a much higher level way of describing things like weak symbols, function definitions and section definitions. This depends on D3105. Differential Revision: http://llvm-reviews.chandlerc.com/D3092 llvm-svn: 204214
2014-03-19 12:47:47 +08:00
COFF-I386-NEXT: SectionDefinition:
COFF-I386-NEXT: Length: 36
COFF-I386-NEXT: NumberOfRelocations: 3
COFF-I386-NEXT: NumberOfLinenumbers: 0
COFF-I386-NEXT: CheckSum: 0
COFF-I386-NEXT: Number: 1
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386: - Name: .data
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386-NEXT: Value: 0
COFF-I386-NEXT: SectionNumber: 2
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-I386-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-I386-NEXT: StorageClass: IMAGE_SYM_CLASS_STATIC
Object: Provide a richer means of describing auxiliary symbols The current state of affairs has auxiliary symbols described as a big bag of bytes. This is less than satisfying, it detracts from the YAML file as being human readable. Instead, allow for symbols to optionally contain their auxiliary data. This allows us to have a much higher level way of describing things like weak symbols, function definitions and section definitions. This depends on D3105. Differential Revision: http://llvm-reviews.chandlerc.com/D3092 llvm-svn: 204214
2014-03-19 12:47:47 +08:00
COFF-I386-NEXT: SectionDefinition:
COFF-I386-NEXT: Length: 13
COFF-I386-NEXT: NumberOfRelocations: 0
COFF-I386-NEXT: NumberOfLinenumbers: 0
COFF-I386-NEXT: CheckSum: 0
COFF-I386-NEXT: Number: 2
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386: - Name: _main
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386-NEXT: Value: 0
COFF-I386-NEXT: SectionNumber: 1
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-I386-NEXT: ComplexType: IMAGE_SYM_DTYPE_FUNCTION
COFF-I386-NEXT: StorageClass: IMAGE_SYM_CLASS_EXTERNAL
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386: - Name: L_.str
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386-NEXT: Value: 0
COFF-I386-NEXT: SectionNumber: 2
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-I386-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-I386-NEXT: StorageClass: IMAGE_SYM_CLASS_STATIC
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386: - Name: _puts
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386-NEXT: Value: 0
COFF-I386-NEXT: SectionNumber: 0
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-I386-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-I386-NEXT: StorageClass: IMAGE_SYM_CLASS_EXTERNAL
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386: - Name: _SomeOtherFunction
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-I386-NEXT: Value: 0
COFF-I386-NEXT: SectionNumber: 0
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-I386-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-I386-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-I386-NEXT: StorageClass: IMAGE_SYM_CLASS_EXTERNAL
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64: header:
COFF-X86-64-NEXT: Machine: IMAGE_FILE_MACHINE_AMD64
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64: sections:
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: - Name: .text
COFF-X86-64-NEXT: Characteristics: [ IMAGE_SCN_CNT_CODE, IMAGE_SCN_MEM_EXECUTE, IMAGE_SCN_MEM_READ ]
COFF-X86-64-NEXT: Alignment: 16
COFF-X86-64-NEXT: SectionData: 4883EC28C744242400000000488D0D00000000E800000000E8000000008B4424244883C428C3
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64: Relocations:
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: - VirtualAddress: 15
Print symbol names in relocations when dumping COFF as YAML. llvm-svn: 183403
2013-06-06 21:06:17 +08:00
COFF-X86-64-NEXT: SymbolName: L.str
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64-NEXT: Type: IMAGE_REL_AMD64_REL32
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64: - VirtualAddress: 20
Print symbol names in relocations when dumping COFF as YAML. llvm-svn: 183403
2013-06-06 21:06:17 +08:00
COFF-X86-64-NEXT: SymbolName: puts
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64-NEXT: Type: IMAGE_REL_AMD64_REL32
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64: - VirtualAddress: 25
Print symbol names in relocations when dumping COFF as YAML. llvm-svn: 183403
2013-06-06 21:06:17 +08:00
COFF-X86-64-NEXT: SymbolName: SomeOtherFunction
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64-NEXT: Type: IMAGE_REL_AMD64_REL32
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64: - Name: .data
COFF-X86-64-NEXT: Characteristics: [ IMAGE_SCN_CNT_INITIALIZED_DATA, IMAGE_SCN_MEM_READ, IMAGE_SCN_MEM_WRITE ]
COFF-X86-64-NEXT: Alignment: 1
COFF-X86-64-NEXT: SectionData: 48656C6C6F20576F726C642100
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
obj2yaml: Use the correct relocation type for different machine types The IO normalizer would essentially lump I386 and AMD64 relocations together. Relocation types with the same numeric value would then get mapped in appropriately. For example: IMAGE_REL_AMD64_ADDR64 and IMAGE_REL_I386_DIR16 both have a numeric value of one. We would see IMAGE_REL_I386_DIR16 in obj2yaml conversions of object files with a machine type of IMAGE_FILE_MACHINE_AMD64. llvm-svn: 205746
2014-04-08 07:12:20 +08:00
COFF-X86-64: - Name: '.CRT$XCU'
COFF-X86-64-NEXT: Characteristics: [ IMAGE_SCN_CNT_INITIALIZED_DATA, IMAGE_SCN_MEM_READ ]
COFF-X86-64-NEXT: Alignment: 8
Revert "Revert "YAMLIO: Encode ambiguous hex strings explicitly"" Don't quote octal compatible strings if they are only two wide, they aren't ambiguous. This reverts commit r205857 which reverted r205857. llvm-svn: 205914
2014-04-10 01:04:27 +08:00
COFF-X86-64-NEXT: SectionData: '0000000000000000'
obj2yaml: Use the correct relocation type for different machine types The IO normalizer would essentially lump I386 and AMD64 relocations together. Relocation types with the same numeric value would then get mapped in appropriately. For example: IMAGE_REL_AMD64_ADDR64 and IMAGE_REL_I386_DIR16 both have a numeric value of one. We would see IMAGE_REL_I386_DIR16 in obj2yaml conversions of object files with a machine type of IMAGE_FILE_MACHINE_AMD64. llvm-svn: 205746
2014-04-08 07:12:20 +08:00
COFF-X86-64: Relocations:
COFF-X86-64-NEXT: - VirtualAddress: 0
COFF-X86-64-NEXT: SymbolName: '??__Ex@@YAXXZ'
COFF-X86-64-NEXT: Type: IMAGE_REL_AMD64_ADDR64
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64: symbols:
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: - Name: .text
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64-NEXT: Value: 0
COFF-X86-64-NEXT: SectionNumber: 1
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-X86-64-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-X86-64-NEXT: StorageClass: IMAGE_SYM_CLASS_STATIC
Object: Provide a richer means of describing auxiliary symbols The current state of affairs has auxiliary symbols described as a big bag of bytes. This is less than satisfying, it detracts from the YAML file as being human readable. Instead, allow for symbols to optionally contain their auxiliary data. This allows us to have a much higher level way of describing things like weak symbols, function definitions and section definitions. This depends on D3105. Differential Revision: http://llvm-reviews.chandlerc.com/D3092 llvm-svn: 204214
2014-03-19 12:47:47 +08:00
COFF-X86-64-NEXT: SectionDefinition:
COFF-X86-64-NEXT: Length: 38
COFF-X86-64-NEXT: NumberOfRelocations: 3
COFF-X86-64-NEXT: NumberOfLinenumbers: 0
COFF-X86-64-NEXT: CheckSum: 0
COFF-X86-64-NEXT: Number: 1
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64: - Name: .data
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64-NEXT: Value: 0
COFF-X86-64-NEXT: SectionNumber: 2
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-X86-64-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-X86-64-NEXT: StorageClass: IMAGE_SYM_CLASS_STATIC
Object: Provide a richer means of describing auxiliary symbols The current state of affairs has auxiliary symbols described as a big bag of bytes. This is less than satisfying, it detracts from the YAML file as being human readable. Instead, allow for symbols to optionally contain their auxiliary data. This allows us to have a much higher level way of describing things like weak symbols, function definitions and section definitions. This depends on D3105. Differential Revision: http://llvm-reviews.chandlerc.com/D3092 llvm-svn: 204214
2014-03-19 12:47:47 +08:00
COFF-X86-64-NEXT: SectionDefinition:
COFF-X86-64-NEXT: Length: 13
COFF-X86-64-NEXT: NumberOfRelocations: 0
COFF-X86-64-NEXT: NumberOfLinenumbers: 0
COFF-X86-64-NEXT: CheckSum: 0
COFF-X86-64-NEXT: Number: 2
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64: - Name: main
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64-NEXT: Value: 0
COFF-X86-64-NEXT: SectionNumber: 1
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
obj2yaml: Use the correct relocation type for different machine types The IO normalizer would essentially lump I386 and AMD64 relocations together. Relocation types with the same numeric value would then get mapped in appropriately. For example: IMAGE_REL_AMD64_ADDR64 and IMAGE_REL_I386_DIR16 both have a numeric value of one. We would see IMAGE_REL_I386_DIR16 in obj2yaml conversions of object files with a machine type of IMAGE_FILE_MACHINE_AMD64. llvm-svn: 205746
2014-04-08 07:12:20 +08:00
COFF-X86-64-NEXT: ComplexType: IMAGE_SYM_DTYPE_FUNCTION
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: StorageClass: IMAGE_SYM_CLASS_EXTERNAL
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64: - Name: L.str
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64-NEXT: Value: 0
COFF-X86-64-NEXT: SectionNumber: 2
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-X86-64-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-X86-64-NEXT: StorageClass: IMAGE_SYM_CLASS_STATIC
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64: - Name: puts
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64-NEXT: Value: 0
COFF-X86-64-NEXT: SectionNumber: 0
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-X86-64-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-X86-64-NEXT: StorageClass: IMAGE_SYM_CLASS_EXTERNAL
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64: - Name: SomeOtherFunction
Add a test for obj2yaml in preparation for refactoring it. llvm-svn: 178829
2013-04-05 10:02:05 +08:00
COFF-X86-64-NEXT: Value: 0
COFF-X86-64-NEXT: SectionNumber: 0
Convert obj2yaml to use yamlio. llvm-svn: 182169
2013-05-18 06:58:42 +08:00
COFF-X86-64-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-X86-64-NEXT: ComplexType: IMAGE_SYM_DTYPE_NULL
COFF-X86-64-NEXT: StorageClass: IMAGE_SYM_CLASS_EXTERNAL
obj2yaml: Use the correct relocation type for different machine types The IO normalizer would essentially lump I386 and AMD64 relocations together. Relocation types with the same numeric value would then get mapped in appropriately. For example: IMAGE_REL_AMD64_ADDR64 and IMAGE_REL_I386_DIR16 both have a numeric value of one. We would see IMAGE_REL_I386_DIR16 in obj2yaml conversions of object files with a machine type of IMAGE_FILE_MACHINE_AMD64. llvm-svn: 205746
2014-04-08 07:12:20 +08:00
COFF-X86-64: - Name: '??__Ex@@YAXXZ'
COFF-X86-64-NEXT: Value: 0
COFF-X86-64-NEXT: SectionNumber: 3
COFF-X86-64-NEXT: SimpleType: IMAGE_SYM_TYPE_NULL
COFF-X86-64-NEXT: ComplexType: IMAGE_SYM_DTYPE_FUNCTION
COFF-X86-64-NEXT: StorageClass: IMAGE_SYM_CLASS_STATIC
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL: FileHeader:
ELF-MIPSEL-NEXT: Class: ELFCLASS32
ELF-MIPSEL-NEXT: Data: ELFDATA2LSB
[Mips] Support SHT_MIPS_ABIFLAGS section type flag in the llvm-readobj, obj2yaml and yaml2obj tools. llvm-svn: 212908
2014-07-13 23:28:54 +08:00
ELF-MIPSEL-NEXT: OSABI: ELFOSABI_GNU
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Type: ET_REL
ELF-MIPSEL-NEXT: Machine: EM_MIPS
[YAML] Add an optional argument `EnumMask` to the `yaml::IO::bitSetCase()`. Some bit-set fields used in ELF file headers in fact contain two parts. The first one is a regular bit-field. The second one is an enumeraion. For example ELF header `e_flags` for MIPS target might contain the following values: Bit-set values: EF_MIPS_NOREORDER = 0x00000001 EF_MIPS_PIC = 0x00000002 EF_MIPS_CPIC = 0x00000004 EF_MIPS_ABI2 = 0x00000020 Enumeration: EF_MIPS_ARCH_32 = 0x50000000 EF_MIPS_ARCH_64 = 0x60000000 EF_MIPS_ARCH_32R2 = 0x70000000 EF_MIPS_ARCH_64R2 = 0x80000000 For printing bit-sets we use the `yaml::IO::bitSetCase()`. It does not support bit-set/enumeration combinations and prints too many flags from an enumeration part. This patch fixes this problem. New method `yaml::IO::maskedBitSetCase()` handle "enumeration" part of bitset defined by provided mask. Patch reviewed by Nick Kledzik and Sean Silva. llvm-svn: 209504
2014-05-23 16:07:09 +08:00
ELF-MIPSEL-NEXT: Flags: [ EF_MIPS_NOREORDER, EF_MIPS_PIC, EF_MIPS_CPIC, EF_MIPS_ABI_O32, EF_MIPS_ARCH_32 ]
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Sections:
ELF-MIPSEL-NEXT: - Name: .text
ELF-MIPSEL-NEXT: Type: SHT_PROGBITS
ELF-MIPSEL-NEXT: Flags: [ SHF_ALLOC, SHF_EXECINSTR ]
ELF-MIPSEL-NEXT: AddressAlign: 0x0000000000000004
ELF-MIPSEL-NEXT: Content: 0000023C00004224E8FFBD271400BFAF1000B0AF218059000000018E000024240000198E09F8200321E000020000198E09F8200321E00002000002241000B08F1400BF8F0800E0031800BD27
ELF-MIPSEL-NEXT: - Name: .rel.text
ELF-MIPSEL-NEXT: Type: SHT_REL
ELF-MIPSEL-NEXT: Link: .symtab
ELF-MIPSEL-NEXT: AddressAlign: 0x0000000000000004
[elf2yaml][ELF] Move Info field to the RelocationSection structure. This field represents ELF section header sh_info field and does not have any sense for regular sections. Its interpretation depends on section type. llvm-svn: 209801
2014-05-29 19:05:31 +08:00
ELF-MIPSEL-NEXT: Info: .text
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Relocations:
[Mips] Support SHT_MIPS_ABIFLAGS section type flag in the llvm-readobj, obj2yaml and yaml2obj tools. llvm-svn: 212908
2014-07-13 23:28:54 +08:00
ELF-MIPSEL-NEXT: - Offset: 0x0000000000000000
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Symbol: _gp_disp
ELF-MIPSEL-NEXT: Type: R_MIPS_HI16
[obj2yaml][ELF] Print relocation's offset as a hex number. Use a proper types to hold relocation's offset and addend. llvm-svn: 208906
2014-05-16 02:04:09 +08:00
ELF-MIPSEL-NEXT: - Offset: 0x0000000000000004
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Symbol: _gp_disp
ELF-MIPSEL-NEXT: Type: R_MIPS_LO16
[obj2yaml][ELF] Print relocation's offset as a hex number. Use a proper types to hold relocation's offset and addend. llvm-svn: 208906
2014-05-16 02:04:09 +08:00
ELF-MIPSEL-NEXT: - Offset: 0x0000000000000018
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Symbol: '$.str'
ELF-MIPSEL-NEXT: Type: R_MIPS_GOT16
[obj2yaml][ELF] Print relocation's offset as a hex number. Use a proper types to hold relocation's offset and addend. llvm-svn: 208906
2014-05-16 02:04:09 +08:00
ELF-MIPSEL-NEXT: - Offset: 0x000000000000001C
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Symbol: '$.str'
ELF-MIPSEL-NEXT: Type: R_MIPS_LO16
[obj2yaml][ELF] Print relocation's offset as a hex number. Use a proper types to hold relocation's offset and addend. llvm-svn: 208906
2014-05-16 02:04:09 +08:00
ELF-MIPSEL-NEXT: - Offset: 0x0000000000000020
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Symbol: puts
ELF-MIPSEL-NEXT: Type: R_MIPS_CALL16
[obj2yaml][ELF] Print relocation's offset as a hex number. Use a proper types to hold relocation's offset and addend. llvm-svn: 208906
2014-05-16 02:04:09 +08:00
ELF-MIPSEL-NEXT: - Offset: 0x000000000000002C
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Symbol: SomeOtherFunction
ELF-MIPSEL-NEXT: Type: R_MIPS_CALL16
ELF-MIPSEL-NEXT: - Name: .data
ELF-MIPSEL-NEXT: Type: SHT_PROGBITS
ELF-MIPSEL-NEXT: Flags: [ SHF_WRITE, SHF_ALLOC ]
ELF-MIPSEL-NEXT: AddressAlign: 0x0000000000000004
ELF-MIPSEL-NEXT: Content: ''
ELF-MIPSEL-NEXT: - Name: .bss
ELF-MIPSEL-NEXT: Type: SHT_NOBITS
ELF-MIPSEL-NEXT: Flags: [ SHF_WRITE, SHF_ALLOC ]
ELF-MIPSEL-NEXT: AddressAlign: 0x0000000000000004
[ELFYAML] Fix handling SHT_NOBITS sections by obj2yaml/yaml2obj tools SHT_NOBITS sections do not have content in an object file. Now the yaml2obj tool does not accept `Content` field for such sections, and the obj2yaml tool does not attempt to read the section content from a file. Restore r241350 and r241352. llvm-svn: 241377
2015-07-04 07:00:54 +08:00
ELF-MIPSEL-NEXT: Size: 0x0000000000000004
[Mips] Support SHT_MIPS_ABIFLAGS section type flag in the llvm-readobj, obj2yaml and yaml2obj tools. llvm-svn: 212908
2014-07-13 23:28:54 +08:00
ELF-MIPSEL-NEXT: - Name: .mdebug.abi32
ELF-MIPSEL-NEXT: Type: SHT_PROGBITS
ELF-MIPSEL-NEXT: AddressAlign: 0x0000000000000001
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Content: ''
ELF-MIPSEL-NEXT: - Name: .rodata.str1.1
ELF-MIPSEL-NEXT: Type: SHT_PROGBITS
ELF-MIPSEL-NEXT: Flags: [ SHF_ALLOC, SHF_MERGE, SHF_STRINGS ]
ELF-MIPSEL-NEXT: AddressAlign: 0x0000000000000001
ELF-MIPSEL-NEXT: Content: 48656C6C6F20576F726C640A00
ELF-MIPSEL-NEXT: - Name: .reginfo
ELF-MIPSEL-NEXT: Type: SHT_MIPS_REGINFO
ELF-MIPSEL-NEXT: Flags: [ SHF_ALLOC ]
ELF-MIPSEL-NEXT: AddressAlign: 0x0000000000000001
ELF-MIPSEL-NEXT: Content: '000000000000000000000000000000000000000000000000'
[Mips] Support SHT_MIPS_ABIFLAGS section type flag in the llvm-readobj, obj2yaml and yaml2obj tools. llvm-svn: 212908
2014-07-13 23:28:54 +08:00
ELF-MIPSEL-NEXT: - Name: .MIPS.abiflags
ELF-MIPSEL-NEXT: Type: SHT_MIPS_ABIFLAGS
ELF-MIPSEL-NEXT: Flags: [ SHF_ALLOC ]
ELF-MIPSEL-NEXT: AddressAlign: 0x0000000000000008
[obj2yaml/yaml2obj] Add SHT_MIPS_ABIFLAGS section support This change adds support for the SHT_MIPS_ABIFLAGS section reading/writing to the obj2yaml and yaml2obj tools. llvm-svn: 236738
2015-05-07 23:40:48 +08:00
ELF-MIPSEL-NEXT: ISA: MIPS32
ELF-MIPSEL-NEXT: ISARevision: 0x01
ELF-MIPSEL-NEXT: FpABI: FP_DOUBLE
ELF-MIPSEL-NEXT: GPRSize: REG_32
ELF-MIPSEL-NEXT: CPR1Size: REG_32
ELF-MIPSEL-NEXT: Flags1: [ ODDSPREG ]
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Symbols:
ELF-MIPSEL-NEXT: Local:
ELF-MIPSEL-NEXT: - Name: trivial.ll
ELF-MIPSEL-NEXT: Type: STT_FILE
ELF-MIPSEL-NEXT: - Name: '$.str'
ELF-MIPSEL-NEXT: Type: STT_OBJECT
ELF-MIPSEL-NEXT: Section: .rodata.str1.1
ELF-MIPSEL-NEXT: Size: 0x000000000000000D
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPSEL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Section: .text
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPSEL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Section: .data
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPSEL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Section: .bss
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPSEL-NEXT: - Type: STT_SECTION
[Mips] Support SHT_MIPS_ABIFLAGS section type flag in the llvm-readobj, obj2yaml and yaml2obj tools. llvm-svn: 212908
2014-07-13 23:28:54 +08:00
ELF-MIPSEL-NEXT: Section: .mdebug.abi32
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPSEL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Section: .rodata.str1.1
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPSEL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Section: .reginfo
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPSEL-NEXT: - Type: STT_SECTION
[Mips] Support SHT_MIPS_ABIFLAGS section type flag in the llvm-readobj, obj2yaml and yaml2obj tools. llvm-svn: 212908
2014-07-13 23:28:54 +08:00
ELF-MIPSEL-NEXT: Section: .MIPS.abiflags
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: Global:
ELF-MIPSEL-NEXT: - Name: main
ELF-MIPSEL-NEXT: Type: STT_FUNC
ELF-MIPSEL-NEXT: Section: .text
ELF-MIPSEL-NEXT: Size: 0x000000000000004C
[Mips] Support SHT_MIPS_ABIFLAGS section type flag in the llvm-readobj, obj2yaml and yaml2obj tools. llvm-svn: 212908
2014-07-13 23:28:54 +08:00
ELF-MIPSEL-NEXT: - Name: var
ELF-MIPSEL-NEXT: Type: STT_OBJECT
ELF-MIPSEL-NEXT: Section: .bss
ELF-MIPSEL-NEXT: Size: 0x0000000000000004
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPSEL-NEXT: - Name: SomeOtherFunction
ELF-MIPSEL-NEXT: - Name: _gp_disp
ELF-MIPSEL-NEXT: - Name: puts
ELF-MIPS64EL: FileHeader:
ELF-MIPS64EL-NEXT: Class: ELFCLASS64
ELF-MIPS64EL-NEXT: Data: ELFDATA2LSB
ELF-MIPS64EL-NEXT: Type: ET_REL
ELF-MIPS64EL-NEXT: Machine: EM_MIPS
[YAML] Add an optional argument `EnumMask` to the `yaml::IO::bitSetCase()`. Some bit-set fields used in ELF file headers in fact contain two parts. The first one is a regular bit-field. The second one is an enumeraion. For example ELF header `e_flags` for MIPS target might contain the following values: Bit-set values: EF_MIPS_NOREORDER = 0x00000001 EF_MIPS_PIC = 0x00000002 EF_MIPS_CPIC = 0x00000004 EF_MIPS_ABI2 = 0x00000020 Enumeration: EF_MIPS_ARCH_32 = 0x50000000 EF_MIPS_ARCH_64 = 0x60000000 EF_MIPS_ARCH_32R2 = 0x70000000 EF_MIPS_ARCH_64R2 = 0x80000000 For printing bit-sets we use the `yaml::IO::bitSetCase()`. It does not support bit-set/enumeration combinations and prints too many flags from an enumeration part. This patch fixes this problem. New method `yaml::IO::maskedBitSetCase()` handle "enumeration" part of bitset defined by provided mask. Patch reviewed by Nick Kledzik and Sean Silva. llvm-svn: 209504
2014-05-23 16:07:09 +08:00
ELF-MIPS64EL-NEXT: Flags: [ EF_MIPS_ARCH_3 ]
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPS64EL-NEXT: Sections:
ELF-MIPS64EL-NEXT: - Name: .text
ELF-MIPS64EL-NEXT: Type: SHT_PROGBITS
ELF-MIPS64EL-NEXT: Flags: [ SHF_ALLOC, SHF_EXECINSTR ]
ELF-MIPS64EL-NEXT: AddressAlign: 0x0000000000000010
ELF-MIPS64EL-NEXT: Content: ''
ELF-MIPS64EL-NEXT: - Name: .data
ELF-MIPS64EL-NEXT: Type: SHT_PROGBITS
ELF-MIPS64EL-NEXT: Flags: [ SHF_WRITE, SHF_ALLOC ]
ELF-MIPS64EL-NEXT: AddressAlign: 0x0000000000000010
ELF-MIPS64EL-NEXT: Content: '00000000000000000000000000000000'
ELF-MIPS64EL-NEXT: - Name: .rela.data
ELF-MIPS64EL-NEXT: Type: SHT_RELA
ELF-MIPS64EL-NEXT: Link: .symtab
ELF-MIPS64EL-NEXT: AddressAlign: 0x0000000000000008
[elf2yaml][ELF] Move Info field to the RelocationSection structure. This field represents ELF section header sh_info field and does not have any sense for regular sections. Its interpretation depends on section type. llvm-svn: 209801
2014-05-29 19:05:31 +08:00
ELF-MIPS64EL-NEXT: Info: .data
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPS64EL-NEXT: Relocations:
ELF-MIPS64EL-NEXT: - Offset: 0
ELF-MIPS64EL-NEXT: Symbol: zed
ELF-MIPS64EL-NEXT: Type: R_MIPS_64
ELF-MIPS64EL-NEXT: - Name: .bss
ELF-MIPS64EL-NEXT: Type: SHT_NOBITS
ELF-MIPS64EL-NEXT: Flags: [ SHF_WRITE, SHF_ALLOC ]
ELF-MIPS64EL-NEXT: AddressAlign: 0x0000000000000010
ELF-MIPS64EL-NEXT: - Name: .MIPS.options
ELF-MIPS64EL-NEXT: Type: SHT_MIPS_OPTIONS
[llvm-readobj][ELF] Teach llvm-readobj to show arch specific ELF section's flags Some architecture specific ELF section flags might have the same value (for example SHF_X86_64_LARGE and SHF_HEX_GPREL) and we have to check machine architectures to select an appropriate set of possible flags. The patch selects architecture specific flags into separate arrays `ElfxxxSectionFlags` and combines `ElfSectionFlags` and `ElfxxxSectionFlags` before pass to the `StreamWriter::printFlags()` method. Differential Revision: http://reviews.llvm.org/D16269 llvm-svn: 258334
2016-01-21 03:15:18 +08:00
ELF-MIPS64EL-NEXT: Flags: [ SHF_ALLOC, SHF_MIPS_NOSTRIP ]
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPS64EL-NEXT: AddressAlign: 0x0000000000000008
ELF-MIPS64EL-NEXT: Content: '01280000000000000000000000000000000000000000000000000000000000000000000000000000'
ELF-MIPS64EL-NEXT: - Name: .pdr
ELF-MIPS64EL-NEXT: Type: SHT_PROGBITS
ELF-MIPS64EL-NEXT: AddressAlign: 0x0000000000000004
ELF-MIPS64EL-NEXT: Content: ''
ELF-MIPS64EL-NEXT: Symbols:
ELF-MIPS64EL-NEXT: Local:
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPS64EL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPS64EL-NEXT: Section: .text
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPS64EL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPS64EL-NEXT: Section: .data
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPS64EL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPS64EL-NEXT: Section: .bss
ELF-MIPS64EL-NEXT: - Name: bar
ELF-MIPS64EL-NEXT: Section: .data
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPS64EL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPS64EL-NEXT: Section: .MIPS.options
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-MIPS64EL-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-MIPS64EL-NEXT: Section: .pdr
ELF-MIPS64EL-NEXT: Global:
ELF-MIPS64EL-NEXT: - Name: zed
ELF-X86-64: FileHeader:
ELF-X86-64-NEXT: Class: ELFCLASS64
ELF-X86-64-NEXT: Data: ELFDATA2LSB
ELF-X86-64-NEXT: OSABI: ELFOSABI_GNU
ELF-X86-64-NEXT: Type: ET_REL
ELF-X86-64-NEXT: Machine: EM_X86_64
ELF-X86-64-NEXT: Sections:
ELF-X86-64-NEXT: - Name: .text
ELF-X86-64-NEXT: Type: SHT_PROGBITS
ELF-X86-64-NEXT: Flags: [ SHF_ALLOC, SHF_EXECINSTR ]
ELF-X86-64-NEXT: AddressAlign: 0x0000000000000010
ELF-X86-64-NEXT: Content: 4883EC08C744240400000000BF00000000E80000000030C0E8000000008B4424044883C408C3
ELF-X86-64-NEXT: - Name: .rodata.str1.1
ELF-X86-64-NEXT: Type: SHT_PROGBITS
ELF-X86-64-NEXT: Flags: [ SHF_ALLOC, SHF_MERGE, SHF_STRINGS ]
ELF-X86-64-NEXT: Address: 0x0000000000000026
ELF-X86-64-NEXT: AddressAlign: 0x0000000000000001
ELF-X86-64-NEXT: Content: 48656C6C6F20576F726C642100
ELF-X86-64-NEXT: - Name: .note.GNU-stack
ELF-X86-64-NEXT: Type: SHT_PROGBITS
ELF-X86-64-NEXT: Address: 0x0000000000000033
ELF-X86-64-NEXT: AddressAlign: 0x0000000000000001
ELF-X86-64-NEXT: Content: ''
ELF-X86-64-NEXT: - Name: .rela.text
ELF-X86-64-NEXT: Type: SHT_RELA
ELF-X86-64-NEXT: Address: 0x0000000000000038
ELF-X86-64-NEXT: Link: .symtab
ELF-X86-64-NEXT: AddressAlign: 0x0000000000000008
[elf2yaml][ELF] Move Info field to the RelocationSection structure. This field represents ELF section header sh_info field and does not have any sense for regular sections. Its interpretation depends on section type. llvm-svn: 209801
2014-05-29 19:05:31 +08:00
ELF-X86-64-NEXT: Info: .text
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-X86-64-NEXT: Relocations:
[obj2yaml][ELF] Print relocation's offset as a hex number. Use a proper types to hold relocation's offset and addend. llvm-svn: 208906
2014-05-16 02:04:09 +08:00
ELF-X86-64-NEXT: - Offset: 0x000000000000000D
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-X86-64-NEXT: Symbol: ''
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-X86-64-NEXT: Type: R_X86_64_32S
[obj2yaml][ELF] Print relocation's offset as a hex number. Use a proper types to hold relocation's offset and addend. llvm-svn: 208906
2014-05-16 02:04:09 +08:00
ELF-X86-64-NEXT: - Offset: 0x0000000000000012
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-X86-64-NEXT: Symbol: puts
ELF-X86-64-NEXT: Type: R_X86_64_PC32
[obj2yaml][ELF] Print relocation's offset as a hex number. Use a proper types to hold relocation's offset and addend. llvm-svn: 208906
2014-05-16 02:04:09 +08:00
ELF-X86-64-NEXT: Addend: -4
ELF-X86-64-NEXT: - Offset: 0x0000000000000019
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-X86-64-NEXT: Symbol: SomeOtherFunction
ELF-X86-64-NEXT: Type: R_X86_64_PC32
[obj2yaml][ELF] Print relocation's offset as a hex number. Use a proper types to hold relocation's offset and addend. llvm-svn: 208906
2014-05-16 02:04:09 +08:00
ELF-X86-64-NEXT: Addend: -4
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-X86-64-NEXT: Symbols:
ELF-X86-64-NEXT: Local:
ELF-X86-64-NEXT: - Name: trivial-object-test.s
ELF-X86-64-NEXT: Type: STT_FILE
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-X86-64-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-X86-64-NEXT: Section: .text
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-X86-64-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-X86-64-NEXT: Section: .rodata.str1.1
Fix the interpretation of a 0 st_name. The ELF spec is very clear: ----------------------------------------------------------------------------- If the value is non-zero, it represents a string table index that gives the symbol name. Otherwise, the symbol table entry has no name. -------------------------------------------------------------------------- In particular, a st_name of 0 most certainly doesn't mean that the symbol has the same name as the section. llvm-svn: 238899
2015-06-03 13:14:22 +08:00
ELF-X86-64-NEXT: - Type: STT_SECTION
[obj2yaml] Support ELF input format in the obj2yaml tool. The ELF header e_flags field in the MIPS related test cases handled incorrectly. The obj2yaml prints too many flags. I will fix that in the next patches. The patch reviewed by Michael Spencer and Sean Silva. llvm-svn: 208752
2014-05-14 13:07:47 +08:00
ELF-X86-64-NEXT: Section: .note.GNU-stack
ELF-X86-64-NEXT: Global:
ELF-X86-64-NEXT: - Name: main
ELF-X86-64-NEXT: Type: STT_FUNC
ELF-X86-64-NEXT: Section: .text
ELF-X86-64-NEXT: Size: 0x0000000000000026
ELF-X86-64-NEXT: - Name: SomeOtherFunction
ELF-X86-64-NEXT: - Name: puts
[ELFYAML] Group ELF section type flags to target specific blocks. Recognize only flags which correspond to the current target. llvm-svn: 212880
2014-07-13 02:25:08 +08:00
[AVR] Add ELF constants to headers Also adds a 'trivial' ELF file. This was generated by assembling and linking a file with the symbol main which contains a single return instruction. llvm-svn: 251096
2015-10-23 14:05:55 +08:00
[WebAssembly] Be consistent in generating trivial test input files For each checked-in wasm file, make sure the there is corresponding .ll file that can be used to regenerate it if needed. Add test/Object/Inputs/trivial-object-test.wasm to match other formats and add some new wasm tests in test/Object. Differential Revision: https://reviews.llvm.org/D35213 llvm-svn: 307585
2017-07-11 04:43:26 +08:00
ELF-AVR: FileHeader:
[AVR] Add ELF constants to headers Also adds a 'trivial' ELF file. This was generated by assembling and linking a file with the symbol main which contains a single return instruction. llvm-svn: 251096
2015-10-23 14:05:55 +08:00
ELF-AVR-NEXT: Class: ELFCLASS32
ELF-AVR-NEXT: Data: ELFDATA2LSB
ELF-AVR-NEXT: Type: ET_EXEC
ELF-AVR-NEXT: Machine: EM_AVR
ELF-AVR-NEXT: Flags: [ EF_AVR_ARCH_AVR2 ]
[WebAssembly] Be consistent in generating trivial test input files For each checked-in wasm file, make sure the there is corresponding .ll file that can be used to regenerate it if needed. Add test/Object/Inputs/trivial-object-test.wasm to match other formats and add some new wasm tests in test/Object. Differential Revision: https://reviews.llvm.org/D35213 llvm-svn: 307585
2017-07-11 04:43:26 +08:00
ELF-AVR-NEXT: Sections:
[AVR] Add ELF constants to headers Also adds a 'trivial' ELF file. This was generated by assembling and linking a file with the symbol main which contains a single return instruction. llvm-svn: 251096
2015-10-23 14:05:55 +08:00
ELF-AVR-NEXT: - Name: .text
ELF-AVR-NEXT: Type: SHT_PROGBITS
ELF-AVR-NEXT: Flags: [ SHF_ALLOC, SHF_EXECINSTR ]
ELF-AVR-NEXT: AddressAlign: 0x0000000000000002
ELF-AVR-NEXT: Content: C20E0895
ELF-AVR-NEXT: - Name: .data
ELF-AVR-NEXT: Type: SHT_PROGBITS
ELF-AVR-NEXT: Flags: [ SHF_WRITE, SHF_ALLOC ]
ELF-AVR-NEXT: Address: 0x0000000000800060
ELF-AVR-NEXT: AddressAlign: 0x0000000000000001
ELF-AVR-NEXT: Content: ''
[WebAssembly] Be consistent in generating trivial test input files For each checked-in wasm file, make sure the there is corresponding .ll file that can be used to regenerate it if needed. Add test/Object/Inputs/trivial-object-test.wasm to match other formats and add some new wasm tests in test/Object. Differential Revision: https://reviews.llvm.org/D35213 llvm-svn: 307585
2017-07-11 04:43:26 +08:00
ELF-AVR-NEXT: Symbols:
ELF-AVR-NEXT: Local:
[AVR] Add ELF constants to headers Also adds a 'trivial' ELF file. This was generated by assembling and linking a file with the symbol main which contains a single return instruction. llvm-svn: 251096
2015-10-23 14:05:55 +08:00
ELF-AVR-NEXT: - Type: STT_SECTION
ELF-AVR-NEXT: Section: .text
ELF-AVR-NEXT: - Type: STT_SECTION
ELF-AVR-NEXT: Section: .data
ELF-AVR-NEXT: Value: 0x0000000000800060
ELF-AVR-NEXT: - Name: a.o
ELF-AVR-NEXT: Type: STT_FILE
ELF-AVR-NEXT: - Name: main
ELF-AVR-NEXT: Section: .text
[WebAssembly] Be consistent in generating trivial test input files For each checked-in wasm file, make sure the there is corresponding .ll file that can be used to regenerate it if needed. Add test/Object/Inputs/trivial-object-test.wasm to match other formats and add some new wasm tests in test/Object. Differential Revision: https://reviews.llvm.org/D35213 llvm-svn: 307585
2017-07-11 04:43:26 +08:00
ELF-AVR-NEXT: Global:
[AVR] Add ELF constants to headers Also adds a 'trivial' ELF file. This was generated by assembling and linking a file with the symbol main which contains a single return instruction. llvm-svn: 251096
2015-10-23 14:05:55 +08:00
ELF-AVR-NEXT: - Name: __trampolines_start
ELF-AVR-NEXT: Section: .text
ELF-AVR-NEXT: - Name: _etext
ELF-AVR-NEXT: Section: .text
ELF-AVR-NEXT: Value: 0x0000000000000004
ELF-AVR-NEXT: - Name: __data_load_end
ELF-AVR-NEXT: Value: 0x0000000000000004
ELF-AVR-NEXT: - Name: __trampolines_end
ELF-AVR-NEXT: Section: .text
ELF-AVR-NEXT: - Name: __data_load_start
ELF-AVR-NEXT: Value: 0x0000000000000004
ELF-AVR-NEXT: - Name: __dtors_end
ELF-AVR-NEXT: Section: .text
ELF-AVR-NEXT: - Name: __eeprom_end
ELF-AVR-NEXT: Section: .data
ELF-AVR-NEXT: Value: 0x0000000000810000
ELF-AVR-NEXT: - Name: __ctors_start
ELF-AVR-NEXT: Section: .text
ELF-AVR-NEXT: - Name: __dtors_start
ELF-AVR-NEXT: Section: .text
ELF-AVR-NEXT: - Name: __ctors_end
ELF-AVR-NEXT: Section: .text
ELF-AVR-NEXT: - Name: _edata
ELF-AVR-NEXT: Section: .data
ELF-AVR-NEXT: Value: 0x0000000000800060
ELF-AVR-NEXT: - Name: _end
ELF-AVR-NEXT: Section: .data
ELF-AVR-NEXT: Value: 0x0000000000800060
[WebAssembly] Be consistent in generating trivial test input files For each checked-in wasm file, make sure the there is corresponding .ll file that can be used to regenerate it if needed. Add test/Object/Inputs/trivial-object-test.wasm to match other formats and add some new wasm tests in test/Object. Differential Revision: https://reviews.llvm.org/D35213 llvm-svn: 307585
2017-07-11 04:43:26 +08:00
WASM: --- !WASM
WASM-NEXT: FileHeader:
WASM-NEXT: Version: 0x00000001
WASM: - Type: EXPORT
WASM-NEXT: Exports:
WASM-NEXT: - Name: main
WASM-NEXT: Kind: FUNCTION
WASM-NEXT: Index: 2
WASM-NEXT: - Name: var
WASM-NEXT: Kind: GLOBAL
WASM-NEXT: Index: 1
[AVR] Add ELF constants to headers Also adds a 'trivial' ELF file. This was generated by assembling and linking a file with the symbol main which contains a single return instruction. llvm-svn: 251096
2015-10-23 14:05:55 +08:00
[ELFYAML] Group ELF section type flags to target specific blocks. Recognize only flags which correspond to the current target. llvm-svn: 212880
2014-07-13 02:25:08 +08:00
ELF-X86-64-UNWIND: - Name: .eh_frame
ELF-X86-64-UNWIND-NEXT: Type: SHT_X86_64_UNWIND
ELF-X86-64-UNWIND-NEXT: Flags: [ SHF_ALLOC ]
ELF-X86-64-UNWIND-NEXT: AddressAlign: 0x0000000000000001
ELF-X86-64-UNWIND-NEXT: Content: ''
[obj2yaml] Fix "time of check to time of use" bug. Add a test. llvm-svn: 248096
2015-09-20 04:49:34 +08:00
Fixup r248096, commit the *correct* test. llvm-svn: 248097
2015-09-20 04:52:47 +08:00
RUN: not obj2yaml %t.blah 2>&1 | FileCheck --check-prefix=ENOENT %s
obj2yaml: Improve error reporting Previously only the error codes were reported which meant that useful information about malformed inputs was not shown. Differential Revision: https://reviews.llvm.org/D34008 llvm-svn: 305609
2017-06-17 07:29:54 +08:00
ENOENT: Error reading file: {{.*}}.blah: {{[Nn]}}o such file or directory