Searched refs:PE32 (Results 1 – 6 of 6) sorted by relevance
8 RUN: | FileCheck %s -check-prefix PE32219 PE32: File: {{(.*[/\\])?}}trivial.exe.coff-i386220 PE32-NEXT: Format: COFF-i386221 PE32-NEXT: Arch: i386222 PE32-NEXT: AddressSize: 32bit223 PE32-NEXT: ImageFileHeader {224 PE32-NEXT: Machine: IMAGE_FILE_MACHINE_I386 (0x14C)225 PE32-NEXT: SectionCount: 3226 PE32-NEXT: TimeDateStamp: 2013-07-16 00:39:15 (0x51E49633)227 PE32-NEXT: PointerToSymbolTable: 0x0[all …]
161 to an EFI binary. EFI binaries are really just PE32+ binaries. PE165 front of it. The "32" in PE32+ stands for 32 bits, meaning that PE32166 is a 32-bit object file format. The plus in "PE32+" indicates that170 than 4GB of address space). EFI binaries are plain PE32+ binaries176 the only difference is the subsystem id. For more details on PE32+,181 In theory, converting a suitable ELF64 binary to PE32+ is easy and191 constitutes those segments. In COFF (and therefore PE32+) no353 As mentioned above, the IA-64 PE32+ format assumes that the entry369 Fortunately, PE32+ defines a section called ".reloc" that can achieve383 create the correct directory entries in the PE32+ binary.
482 PE32 = 0x10b, enumerator
487 PE32 = 0x10b, enumerator
406 uint32_t BaseOfData = initializeOptionalHeader(CP, COFF::PE32Header::PE32, &PEH); in writeCOFF()
704 if (Header->Magic == COFF::PE32Header::PE32) { in COFFObjectFile()