Files
clang-p2996/llvm/test/tools/yaml2obj/ELF/output-limit.yaml
Georgii Rymar a6436b0b3a [yaml2obj] - Make the 'Machine' key optional.
Currently we have to set 'Machine' to something in our
YAML descriptions. Usually we use 'EM_X86_64' for 64-bit targets
and 'EM_386' for 32-bit targets. At the same time, in fact, in most
cases our tests do not need a machine type and we can use
'EM_NONE'.

This is cleaner, because avoids the need of using a particular machine.

In this patch I've made the 'Machine' key optional (the default value,
when it is not specified is `EM_NONE`) and removed it (where possible)
from yaml2obj, obj2yaml and llvm-readobj tests.

There are few tests left where I decided not to remove it, because
I didn't want to touch CHECK lines or doing anything more complex
than a removing a "Machine: *" line and formatting lines around.

Differential revision: https://reviews.llvm.org/D86202
2020-08-20 11:40:51 +03:00

54 lines
1.7 KiB
YAML

## Check that yaml2obj limits the output size by default to 10 MB.
## Check it is possible to change this limit using the
## --max-size command line option.
## One of the often cases to reach the limit is to create a section with a
## large portion of data. Check this case is handled properly.
## 0x9FFEC0 = 0xA00000 (10 MB) - sizeof(Elf_Ehdr) - sizeof(Elf_Shdr) * 4.
# RUN: yaml2obj %s -DSIZE=0x9FFEC0 --docnum=1 -o /dev/null 2>&1
# RUN: not yaml2obj %s -DSIZE=0x9FFEC1 --docnum=1 -o /dev/null 2>&1 | \
# RUN: FileCheck %s --check-prefix=ERROR
# ERROR: error: the desired output size is greater than permitted. Use the --max-size option to change the limit
## We use 0xA00008 instead of 0xA00001 here because the section header table
## offset is aligned to 8 bytes, so we need to request 7 more bytes for it.
# RUN: yaml2obj %s -DSIZE=0x9FFEC1 --docnum=1 --max-size=0xA00008 -o /dev/null
--- !ELF
FileHeader:
Class: ELFCLASS64
Data: ELFDATA2LSB
Type: ET_REL
Sections:
- Name: .section
Type: SHT_PROGBITS
Size: [[SIZE]]
- Name: .strtab
Type: SHT_PROGBITS
Size: 0x0
- Name: .shstrtab
Type: SHT_PROGBITS
Size: 0x0
## Another possible case is when an alignment gap inserted
## is too large because of overaligning. Check it is also handled properly.
# RUN: not yaml2obj %s --docnum=2 -o /dev/null 2>&1 | FileCheck %s --check-prefix=ERROR
--- !ELF
FileHeader:
Class: ELFCLASS64
Data: ELFDATA2LSB
Type: ET_REL
Sections:
- Name: .foo
Type: SHT_PROGBITS
- Name: .bar
Type: SHT_PROGBITS
AddressAlign: 0xA00100
Size: 0x0
## Check that we can drop the limit with the use of --max-size=0.
# RUN: yaml2obj --max-size=0 %s --docnum=2 -o /dev/null