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
56 lines
1.9 KiB
YAML
56 lines
1.9 KiB
YAML
## Show how yaml2obj sets physical and virtual addresses of program headers.
|
|
|
|
# RUN: yaml2obj %s -o %t
|
|
# RUN: llvm-readelf --sections --segments %t | FileCheck %s
|
|
|
|
# CHECK: Section Headers:
|
|
# CHECK: [Nr] Name Type Address Off Size ES Flg
|
|
# CHECK: [ 1] .foo PROGBITS 0000000000001234 000120 000001 00 A
|
|
|
|
# CHECK: Program Headers:
|
|
# CHECK-NEXT: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
|
|
# CHECK-NEXT: LOAD 0x000000 0x0000000000000000 0x0000000000000000 0x000000 0x000000 R E 0x1
|
|
# CHECK-NEXT: LOAD 0x000120 0x0000000000000000 0x0000000000000000 0x000001 0x000001 R E 0x1
|
|
# CHECK-NEXT: LOAD 0x000120 0x00000000aaaa1000 0x00000000aaaa1000 0x000001 0x000001 R E 0x1
|
|
# CHECK-NEXT: LOAD 0x000120 0x00000000aaaa1000 0x00000000bbbb2000 0x000001 0x000001 R E 0x1
|
|
|
|
--- !ELF
|
|
FileHeader:
|
|
Class: ELFCLASS64
|
|
Data: ELFDATA2LSB
|
|
Type: ET_EXEC
|
|
Sections:
|
|
- Name: .foo
|
|
Type: SHT_PROGBITS
|
|
Flags: [ SHF_ALLOC ]
|
|
Size: 0x1
|
|
Address: 0x1234
|
|
ProgramHeaders:
|
|
## Show what virtual and physical address we set by default for the case where
|
|
## a program header has no sections.
|
|
- Type: PT_LOAD
|
|
Flags: [ PF_X, PF_R ]
|
|
Sections: []
|
|
## Show what virtual and physical address we set by default for the case
|
|
## where a program header includes a section with a virtual address that
|
|
## is explicitly set.
|
|
- Type: PT_LOAD
|
|
Flags: [ PF_X, PF_R ]
|
|
Sections:
|
|
- Section: .foo
|
|
## Now we have a program header that has a virtual address different to
|
|
## the address of the section included. Show that the default physical address
|
|
## is equal to the program header's virtual address.
|
|
- Type: PT_LOAD
|
|
Flags: [ PF_X, PF_R ]
|
|
VAddr: 0xAAAA1000
|
|
Sections:
|
|
- Section: .foo
|
|
## Show that we are able to set different virtual and physical addresses.
|
|
- Type: PT_LOAD
|
|
Flags: [ PF_X, PF_R ]
|
|
VAddr: 0xAAAA1000
|
|
PAddr: 0xBBBB2000
|
|
Sections:
|
|
- Section: .foo
|