replica
/
hanchenye-llvm-project
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
hanchenye-llvm-project/lld/test/pecoff/trivial.test

85 lines
3.1 KiB
Plaintext
Raw Normal View History

[PECOFF] Rename basic.test -> trivial.test. Because the test does not actually cover basic features. llvm-svn: 183870
2013-06-13 06:19:05 +08:00
# Checks functionality of PECOFF writer. "nop.obj" is an object that has only
# text section. Other data, including data sections, relocations, symbol
# tables are not present in nop.obj.
#
[PECOFF] Use yaml2obj to avoid checking in binary files. llvm-svn: 185690
2013-07-05 18:41:44 +08:00
# RUN: yaml2obj %p/Inputs/nop.obj.yaml > %t.obj
#
[PECOFF] Add file extensions to temporary files. No functionality change. llvm-svn: 198075
2013-12-27 16:37:40 +08:00
# RUN: lld -flavor link /out:%t1.exe /subsystem:console,3.11 /version:1.25 \
# RUN: /entry:start /opt:noref -- %t.obj
# RUN: llvm-readobj -file-headers %t1.exe | FileCheck -check-prefix=FILE %s
[PECOFF] Use yaml2obj to avoid checking in binary files. llvm-svn: 185690
2013-07-05 18:41:44 +08:00
#
[PECOFF] Add file extensions to temporary files. No functionality change. llvm-svn: 198075
2013-12-27 16:37:40 +08:00
# RUN: lld -flavor link /out:%t2.exe /subsystem:console /entry:start \
# RUN: /opt:noref -- %t.obj
# RUN: llvm-readobj -sections %t2.exe | FileCheck -check-prefix=SECTIONS %s
[lld][PECOFF] Add WinLinkDriver and PECOFFTargetInfo. Add WinLinkDriver and connect it to the existing COFF reader. Remaining parts are still stubs, so while it can now read a COFF file, it still cannot link or output PE/COFF files yet. Reviewers: Bigcheese CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D865 llvm-svn: 182784
2013-05-29 02:13:31 +08:00
[PECOFF] Add a generic section writer. Instead of having multiple SectionChunks for each section (.text, .data, .rdata and .bss), we could have one chunk writer that can emit any sections. This patch does that -- removing all section-sepcific chunk writers and replace them with one "generic" writer. This change should simplify the code because it eliminates similar-but- slightly-different classes. It also fixes an issue in the previous design. Before this patch, we could emit only limited set of sections (i.e. .text, .data, .rdata and .bss). With this patch, we can emit any sections. llvm-svn: 195797
2013-11-27 08:55:45 +08:00
FILE: Format: COFF-i386
FILE-NEXT: Arch: i386
FILE-NEXT: AddressSize: 32bit
FILE-NEXT: ImageFileHeader {
FILE-NEXT: Machine: IMAGE_FILE_MACHINE_I386 (0x14C)
[PECOFF] Do not emit a section if it's empty. The PE32+ loader does not seem to like an executable with an empty section, so we should not emit a section if it's empty. llvm-svn: 200514
2014-01-31 13:15:42 +08:00
FILE-NEXT: SectionCount: 1
[PECOFF] Add a generic section writer. Instead of having multiple SectionChunks for each section (.text, .data, .rdata and .bss), we could have one chunk writer that can emit any sections. This patch does that -- removing all section-sepcific chunk writers and replace them with one "generic" writer. This change should simplify the code because it eliminates similar-but- slightly-different classes. It also fixes an issue in the previous design. Before this patch, we could emit only limited set of sections (i.e. .text, .data, .rdata and .bss). With this patch, we can emit any sections. llvm-svn: 195797
2013-11-27 08:55:45 +08:00
FILE-NEXT: TimeDateStamp:
FILE-NEXT: PointerToSymbolTable: 0x0
FILE-NEXT: SymbolCount: 0
FILE-NEXT: OptionalHeaderSize: 224
FILE-NEXT: Characteristics [ (0x102)
FILE-NEXT: IMAGE_FILE_32BIT_MACHINE (0x100)
FILE-NEXT: IMAGE_FILE_EXECUTABLE_IMAGE (0x2)
FILE-NEXT: ]
FILE-NEXT: }
FILE-NEXT: ImageOptionalHeader {
FILE-NEXT: MajorLinkerVersion: 0
FILE-NEXT: MinorLinkerVersion: 0
[PECOFF] Writer: Remove NULL padding at the end of each section. If section size is not multiple of 512, the writer added NULL bytes at the end of it to make it so. That is not required by the PE/COFF spec, and the MSVC's linker does not do that too. So we don't need to do that, too. llvm-svn: 197002
2013-12-11 12:06:26 +08:00
FILE-NEXT: SizeOfCode: 6
[PECOFF] Add a generic section writer. Instead of having multiple SectionChunks for each section (.text, .data, .rdata and .bss), we could have one chunk writer that can emit any sections. This patch does that -- removing all section-sepcific chunk writers and replace them with one "generic" writer. This change should simplify the code because it eliminates similar-but- slightly-different classes. It also fixes an issue in the previous design. Before this patch, we could emit only limited set of sections (i.e. .text, .data, .rdata and .bss). With this patch, we can emit any sections. llvm-svn: 195797
2013-11-27 08:55:45 +08:00
FILE-NEXT: SizeOfInitializedData: 0
FILE-NEXT: SizeOfUninitializedData: 0
FILE-NEXT: AddressOfEntryPoint: 0x1000
FILE-NEXT: BaseOfCode: 0x1000
FILE-NEXT: BaseOfData: 0
FILE-NEXT: ImageBase: 0x400000
FILE-NEXT: SectionAlignment: 4096
FILE-NEXT: FileAlignment: 512
FILE-NEXT: MajorOperatingSystemVersion: 3
FILE-NEXT: MinorOperatingSystemVersion: 11
FILE-NEXT: MajorImageVersion: 1
FILE-NEXT: MinorImageVersion: 25
FILE-NEXT: MajorSubsystemVersion: 3
FILE-NEXT: MinorSubsystemVersion: 11
FILE-NEXT: SizeOfImage: 8192
FILE-NEXT: SizeOfHeaders: 512
FILE-NEXT: Subsystem: IMAGE_SUBSYSTEM_WINDOWS_CUI (0x3)
[PECOFF] Emit Load Configuration and SEH Table for x86. If all input files are compatible with Structured Exception Handling, linker is supposed to create an exectuable with a table for SEH handlers. The table consists of exception handlers entry point addresses. The basic idea of SEH in x86 Microsoft ABI is to list all valid entry points of exception handlers in an read-only memory, so that an attacker cannot override the addresses in it. In x86 ABI, data for exception handling is mostly on stack, so it's volnerable to stack overflow attack. In order to protect against it, Windows runtime uses the table to check a return address, to ensure that the address is really an valid entry point for an exception handler. Compiler emits a list of exception handler functions to .sxdata section. It also emits a marker symbol "@feat.00" to indicate that the object is compatible with SEH. SEH is a relatively new feature for COFF, and mixing SEH-compatible and SEH-incompatible objects will result in an invalid executable, so is the marker. If all input files are compatible with SEH, LLD emits a SEH table. SEH table needs to be pointed by Load Configuration strucutre, so when emitting a SEH table LLD emits it too. The address of a Load Configuration will be stored to the file header. llvm-svn: 202248
2014-02-26 16:27:59 +08:00
FILE-NEXT: Subsystem [ (0x8540)
[PECOFF] Add a generic section writer. Instead of having multiple SectionChunks for each section (.text, .data, .rdata and .bss), we could have one chunk writer that can emit any sections. This patch does that -- removing all section-sepcific chunk writers and replace them with one "generic" writer. This change should simplify the code because it eliminates similar-but- slightly-different classes. It also fixes an issue in the previous design. Before this patch, we could emit only limited set of sections (i.e. .text, .data, .rdata and .bss). With this patch, we can emit any sections. llvm-svn: 195797
2013-11-27 08:55:45 +08:00
FILE-NEXT: IMAGE_DLL_CHARACTERISTICS_DYNAMIC_BASE (0x40)
[PECOFF] Emit Load Configuration and SEH Table for x86. If all input files are compatible with Structured Exception Handling, linker is supposed to create an exectuable with a table for SEH handlers. The table consists of exception handlers entry point addresses. The basic idea of SEH in x86 Microsoft ABI is to list all valid entry points of exception handlers in an read-only memory, so that an attacker cannot override the addresses in it. In x86 ABI, data for exception handling is mostly on stack, so it's volnerable to stack overflow attack. In order to protect against it, Windows runtime uses the table to check a return address, to ensure that the address is really an valid entry point for an exception handler. Compiler emits a list of exception handler functions to .sxdata section. It also emits a marker symbol "@feat.00" to indicate that the object is compatible with SEH. SEH is a relatively new feature for COFF, and mixing SEH-compatible and SEH-incompatible objects will result in an invalid executable, so is the marker. If all input files are compatible with SEH, LLD emits a SEH table. SEH table needs to be pointed by Load Configuration strucutre, so when emitting a SEH table LLD emits it too. The address of a Load Configuration will be stored to the file header. llvm-svn: 202248
2014-02-26 16:27:59 +08:00
FILE-NEXT: IMAGE_DLL_CHARACTERISTICS_NO_SEH (0x400)
[PECOFF] Add a generic section writer. Instead of having multiple SectionChunks for each section (.text, .data, .rdata and .bss), we could have one chunk writer that can emit any sections. This patch does that -- removing all section-sepcific chunk writers and replace them with one "generic" writer. This change should simplify the code because it eliminates similar-but- slightly-different classes. It also fixes an issue in the previous design. Before this patch, we could emit only limited set of sections (i.e. .text, .data, .rdata and .bss). With this patch, we can emit any sections. llvm-svn: 195797
2013-11-27 08:55:45 +08:00
FILE-NEXT: IMAGE_DLL_CHARACTERISTICS_NX_COMPAT (0x100)
FILE-NEXT: IMAGE_DLL_CHARACTERISTICS_TERMINAL_SERVER_AWARE (0x8000)
FILE-NEXT: ]
FILE-NEXT: SizeOfStackReserve: 1048576
FILE-NEXT: SizeOfStackCommit: 4096
FILE-NEXT: SizeOfHeapReserve: 1048576
FILE-NEXT: SizeOfHeapCommit: 4096
FILE-NEXT: NumberOfRvaAndSize: 16
[PECOFF][Writer] Implement the writer that can emit text section. lld can now output a valid Windows executable with a text section that does nothing but just returns immediately. It's not able to handle relocations, symbol tables, data sections, etc, so it still can't do anything practical, though. Reviewers: Bigcheese CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D892 llvm-svn: 183478
2013-06-07 09:31:51 +08:00
[PECOFF] Add a generic section writer. Instead of having multiple SectionChunks for each section (.text, .data, .rdata and .bss), we could have one chunk writer that can emit any sections. This patch does that -- removing all section-sepcific chunk writers and replace them with one "generic" writer. This change should simplify the code because it eliminates similar-but- slightly-different classes. It also fixes an issue in the previous design. Before this patch, we could emit only limited set of sections (i.e. .text, .data, .rdata and .bss). With this patch, we can emit any sections. llvm-svn: 195797
2013-11-27 08:55:45 +08:00
SECTIONS: Format: COFF-i386
SECTIONS-NEXT: Arch: i386
SECTIONS-NEXT: AddressSize: 32bit
SECTIONS-NEXT: Sections [
SECTIONS-NEXT: Section {
SECTIONS-NEXT: Number: 1
SECTIONS-NEXT: Name: .text (2E 74 65 78 74 00 00 00)
SECTIONS-NEXT: VirtualSize: 0x6
SECTIONS-NEXT: VirtualAddress: 0x1000
[PECOFF] Writer: Remove NULL padding at the end of each section. If section size is not multiple of 512, the writer added NULL bytes at the end of it to make it so. That is not required by the PE/COFF spec, and the MSVC's linker does not do that too. So we don't need to do that, too. llvm-svn: 197002
2013-12-11 12:06:26 +08:00
SECTIONS-NEXT: RawDataSize: 6
[PECOFF] Add a generic section writer. Instead of having multiple SectionChunks for each section (.text, .data, .rdata and .bss), we could have one chunk writer that can emit any sections. This patch does that -- removing all section-sepcific chunk writers and replace them with one "generic" writer. This change should simplify the code because it eliminates similar-but- slightly-different classes. It also fixes an issue in the previous design. Before this patch, we could emit only limited set of sections (i.e. .text, .data, .rdata and .bss). With this patch, we can emit any sections. llvm-svn: 195797
2013-11-27 08:55:45 +08:00
SECTIONS-NEXT: PointerToRawData: 0x200
SECTIONS-NEXT: PointerToRelocations: 0x0
SECTIONS-NEXT: PointerToLineNumbers: 0x0
SECTIONS-NEXT: RelocationCount: 0
SECTIONS-NEXT: LineNumberCount: 0
SECTIONS-NEXT: Characteristics [
SECTIONS-NEXT: IMAGE_SCN_CNT_CODE
SECTIONS-NEXT: IMAGE_SCN_MEM_EXECUTE
SECTIONS-NEXT: IMAGE_SCN_MEM_READ
SECTIONS-NEXT: ]
SECTIONS-NEXT: }
SECTIONS-NEXT: ]