llvm-project/llvm/test/Object/yaml2obj-elf-symbol-LocalGl...

# RUN: yaml2obj %s | llvm-readobj -symbols - | FileCheck %s
!ELF
FileHeader:
  Class: ELFCLASS64
  Data: ELFDATA2LSB
  Type: ET_REL
  Machine: EM_X86_64
Sections:
  - Name: .data
    Type: SHT_PROGBITS
    Flags: [ SHF_ALLOC, SHF_WRITE ]
    Content: "DEADBEEF"
Symbols:
  Local:
    - Name: local_symbol
      Type: STT_OBJECT
      Section: .data
  Global:
    - Name: global_symbol
      Type: STT_OBJECT
      Section: .data
  Weak:
    - Name: weak_symbol
      Type: STT_OBJECT
      Section: .data

# CHECK: Symbol {
# CHECK:   Name:  (0)
# CHECK: Symbol {
# CHECK:   Name: local_symbol
# CHECK:   Binding: Local
# CHECK: Symbol {
# CHECK:   Name: global_symbol
# CHECK:   Binding: Global
# CHECK: Symbol {
# CHECK:   Name: weak_symbol
# CHECK:   Binding: Weak
[yaml2obj] Remove --format option in favor of YAML tags Summary: Our YAML library's handling of tags isn't perfect, but it is good enough to get rid of the need for the --format argument to yaml2obj. This patch does exactly that. Instead of requiring --format, it infers the format based on the tags found in the object file. The supported tags are: !ELF !COFF !mach-o !fat-mach-o I have a corresponding patch that is quite large that fixes up all the in-tree test cases. Reviewers: rafael, Bigcheese, compnerd, silvas Subscribers: compnerd, llvm-commits Differential Revision: http://reviews.llvm.org/D21711 llvm-svn: 273915 2016-06-28 03:53:53 +08:00			`# RUN: yaml2obj %s \| llvm-readobj -symbols - \| FileCheck %s`
[yaml2obj][ELF] Don't explicitly set `Binding` with STB_* Instead, just have 3 sub-lists, one for each of {STB_LOCAL,STB_GLOBAL,STB_WEAK}. This allows us to be a lot more explicit w.r.t. the symbol ordering in the object file, because if we allowed explicitly setting the STB_* `Binding` key for the symbol, then we might have ended up having to shuffle STB_LOCAL symbols to the front of the list, which is likely to cause confusion and potential for error. Also, this new approach is simpler ;) llvm-svn: 184506 2013-06-21 08:27:50 +08:00			`!ELF`
			`FileHeader:`
			`Class: ELFCLASS64`
			`Data: ELFDATA2LSB`
			`Type: ET_REL`
			`Machine: EM_X86_64`
			`Sections:`
			`- Name: .data`
			`Type: SHT_PROGBITS`
			`Flags: [ SHF_ALLOC, SHF_WRITE ]`
			`Content: "DEADBEEF"`
[yaml2obj][ELF] Make symbol table top-level key. Although in reality the symbol table in ELF resides in a section, the standard requires that there be no more than one SHT_SYMTAB. To enforce this constraint, it is cleaner to group all the symbols under a top-level `Symbols` key on the object file. llvm-svn: 184627 2013-06-22 09:38:00 +08:00			`Symbols:`
			`Local:`
			`- Name: local_symbol`
			`Type: STT_OBJECT`
			`Section: .data`
			`Global:`
			`- Name: global_symbol`
			`Type: STT_OBJECT`
			`Section: .data`
			`Weak:`
			`- Name: weak_symbol`
			`Type: STT_OBJECT`
			`Section: .data`
[yaml2obj][ELF] Don't explicitly set `Binding` with STB_* Instead, just have 3 sub-lists, one for each of {STB_LOCAL,STB_GLOBAL,STB_WEAK}. This allows us to be a lot more explicit w.r.t. the symbol ordering in the object file, because if we allowed explicitly setting the STB_* `Binding` key for the symbol, then we might have ended up having to shuffle STB_LOCAL symbols to the front of the list, which is likely to cause confusion and potential for error. Also, this new approach is simpler ;) llvm-svn: 184506 2013-06-21 08:27:50 +08:00
			`# CHECK: Symbol {`
			`# CHECK: Name: (0)`
			`# CHECK: Symbol {`
			`# CHECK: Name: local_symbol`
			`# CHECK: Binding: Local`
			`# CHECK: Symbol {`
			`# CHECK: Name: global_symbol`
			`# CHECK: Binding: Global`
			`# CHECK: Symbol {`
			`# CHECK: Name: weak_symbol`
			`# CHECK: Binding: Weak`