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

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

36 lines
898 B
Plaintext
Raw Normal View History

[test] Use yaml2obj -o %t instead of > %t To improve consistency and avoid unneeded shell feature (output redirection). While here, make other changes to improve consistency --docnum 1 => --docnum=1 -docnum=x => --docnum=x
2020-01-22 09:02:25 +08:00
# RUN: yaml2obj %s -o %t.o
[DWARF] - Add testcase for checking message about broken relocations. Addresses comments for r306677, which fixed error message itself. llvm-svn: 307655
2017-07-11 20:29:07 +08:00
# RUN: llvm-dwarfdump %t.o 2>&1 | FileCheck %s
# CHECK: failed to compute relocation: Unknown
!ELF
FileHeader:
Class: ELFCLASS32
Data: ELFDATA2LSB
Type: ET_REL
Machine: EM_386
Sections:
- Type: SHT_PROGBITS
Name: .text
Flags: [ ]
AddressAlign: 0x04
Content: "0000"
- Type: SHT_PROGBITS
Name: .debug_info
Flags: [ ]
AddressAlign: 0x04
Content: "0000"
- Type: SHT_REL
Name: .rel.debug_info
Link: .symtab
Info: .debug_info
Relocations:
- Offset: 0
Symbol: _start
Type: 0xFF
Symbols:
[yaml2obj][obj2yaml] - Change how symbol's binding is descibed when parsing/dumping. Currently, YAML has the following syntax for describing the symbols: Symbols: Local: LocalSymbol1: ... LocalSymbol2: ... ... Global: GlobalSymbol1: ... Weak: ... GNUUnique: I.e. symbols are grouped by their bindings. That is not very convenient, because: It does not allow to set a custom binding, what can be useful for producing broken/special outputs for test cases. Adding a new binding would require to change a syntax (what we observed when added GNUUnique recently). It does not allow to change the order of the symbols in .symtab/.dynsym, i.e. currently all Local symbols are placed first, then Global, Weak and GNUUnique are following, but we are not able to change the order. It is not consistent. Binding is just one of the properties of the symbol, we do not group them by other properties. It makes the code more complex that it can be. This patch shows it can be simplified with the change performed. The patch changes the syntax to just: Symbols: Symbol1: ... Symbol2: ... ... With that, we are able to work with the binding field just like with any other symbol property. Differential revision: https://reviews.llvm.org/D60122 llvm-svn: 357595
2019-04-03 22:53:42 +08:00
- Name: _start
Type: STT_FUNC
Section: .text
Value: 0x0
Binding: STB_GLOBAL