a6436b0b3a
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
15 lines
321 B
YAML
15 lines
321 B
YAML
## We have a YAML file describing an invalid data type.
|
|
## Check we are able to produce the invalid binary.
|
|
|
|
# RUN: yaml2obj %s -o %t.o
|
|
|
|
## Check that EI_DATA field is ELFDATANONE(0)
|
|
# RUN: od -b %t.o +5 | FileCheck %s
|
|
# CHECK: 0000005 000
|
|
|
|
--- !ELF
|
|
FileHeader:
|
|
Class: ELFCLASS64
|
|
Data: ELFDATANONE
|
|
Type: ET_REL
|