maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/ELF/i386-pc16.test

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

40 lines
1003 B
Plaintext
Raw Normal View History

[ELF] - Implemented R_386_16 and R_386PC16 relocations A program or object file using R_386_8, R_386_16, R_386_PC16 or R_386_PC8 relocations is not conformant to latest ABI. The R_386_16, and R_386_8 relocations truncate the computed value to 16 - bits and 8 - bits respectively. R_386_PC16 and R_386_16 are used by some applications, for example by FreeBSD loaders. Previously we did not take addend in account for these relocation, counting it as 0, what is wrong and was a reason of hangs. This patch needed for example for FreeBSD pmbr (protective mbr). Differential revision: https://reviews.llvm.org/D27303 llvm-svn: 288581
2016-12-03 15:30:30 +08:00
# REQUIRES: x86
# RUN: yaml2obj %s -o %t.o
[ELF] - Change i386 i386-pc8.s/i386-pc16.test to work with 8/16 bits values accordingly. ld.bfd showed error on previous inputs, result values were larger than 8/16 bits, though ld.gold accepted them. ABI says "The R_386_16, and R_386_8 relocations truncate the computed value to 16-bits and 8-bits respectively". Patch changes inputs to have result calculated values of relocations to fit 8 and 16 bits. That can be used for implementation of more strict checks, like bfd do. Differential revision: https://reviews.llvm.org/D29270 llvm-svn: 293479
2017-01-30 21:56:57 +08:00
# RUN: ld.lld -Ttext 0x0 %t.o -o %t.exe
[test] lld/test/: change llvm-objdump single-dash long options to double-dash options
2020-03-16 08:47:44 +08:00
# RUN: llvm-objdump -s --section=.text %t.exe 2>&1 | FileCheck %s
[ELF] - Implemented R_386_16 and R_386PC16 relocations A program or object file using R_386_8, R_386_16, R_386_PC16 or R_386_PC8 relocations is not conformant to latest ABI. The R_386_16, and R_386_8 relocations truncate the computed value to 16 - bits and 8 - bits respectively. R_386_PC16 and R_386_16 are used by some applications, for example by FreeBSD loaders. Previously we did not take addend in account for these relocation, counting it as 0, what is wrong and was a reason of hangs. This patch needed for example for FreeBSD pmbr (protective mbr). Differential revision: https://reviews.llvm.org/D27303 llvm-svn: 288581
2016-12-03 15:30:30 +08:00
# CHECK: Contents of section .text:
[ELF] - Change i386 i386-pc8.s/i386-pc16.test to work with 8/16 bits values accordingly. ld.bfd showed error on previous inputs, result values were larger than 8/16 bits, though ld.gold accepted them. ABI says "The R_386_16, and R_386_8 relocations truncate the computed value to 16-bits and 8-bits respectively". Patch changes inputs to have result calculated values of relocations to fit 8 and 16 bits. That can be used for implementation of more strict checks, like bfd do. Differential revision: https://reviews.llvm.org/D29270 llvm-svn: 293479
2017-01-30 21:56:57 +08:00
# CHECK-NEXT: 0000 45231111 41231111
[ELF] - Implemented R_386_16 and R_386PC16 relocations A program or object file using R_386_8, R_386_16, R_386_PC16 or R_386_PC8 relocations is not conformant to latest ABI. The R_386_16, and R_386_8 relocations truncate the computed value to 16 - bits and 8 - bits respectively. R_386_PC16 and R_386_16 are used by some applications, for example by FreeBSD loaders. Previously we did not take addend in account for these relocation, counting it as 0, what is wrong and was a reason of hangs. This patch needed for example for FreeBSD pmbr (protective mbr). Differential revision: https://reviews.llvm.org/D27303 llvm-svn: 288581
2016-12-03 15:30:30 +08:00
!ELF
FileHeader:
Class: ELFCLASS32
Data: ELFDATA2LSB
Type: ET_REL
Machine: EM_386
Sections:
- Type: SHT_PROGBITS
Name: .text
Flags: [ SHF_ALLOC, SHF_EXECINSTR ]
AddressAlign: 0x04
Content: "1111111111111111"
- Type: SHT_REL
Name: .rel.text
Link: .symtab
Info: .text
AddressAlign: 0x04
Relocations:
[lib/ObjectYAML] - Make `ELFYAML::Relocation::Offset` optional. Currently `yaml2obj` require `Offset` field in a relocation description. There are many cases when `Offset` is insignificant in a context of a test case. Making `Offset` optional allows to simplify our test cases. This is what this patch does. Also, with this patch `obj2yaml` does not dump a zero offset of a relocation. Differential revision: https://reviews.llvm.org/D75608
2020-03-04 21:55:15 +08:00
- Symbol: _start
[ELF] - Implemented R_386_16 and R_386PC16 relocations A program or object file using R_386_8, R_386_16, R_386_PC16 or R_386_PC8 relocations is not conformant to latest ABI. The R_386_16, and R_386_8 relocations truncate the computed value to 16 - bits and 8 - bits respectively. R_386_PC16 and R_386_16 are used by some applications, for example by FreeBSD loaders. Previously we did not take addend in account for these relocation, counting it as 0, what is wrong and was a reason of hangs. This patch needed for example for FreeBSD pmbr (protective mbr). Differential revision: https://reviews.llvm.org/D27303 llvm-svn: 288581
2016-12-03 15:30:30 +08:00
Type: R_386_16
- Offset: 4
Symbol: _start
Type: R_386_PC16
Symbols:
[LLD] - Update the test cases after yaml2obj change. https://reviews.llvm.org/D60122 (r357595) changed the symbols description format. This change updates the LLD tests. llvm-svn: 357596
2019-04-03 22:54:22 +08:00
- Name: _start
Type: STT_FUNC
Section: .text
Value: 0x1234
Size: 4
Binding: STB_GLOBAL