maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lld/test/COFF/loadcfg32.test

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

59 lines
1.9 KiB
Plaintext
Raw Normal View History

[test] Replace `yaml2obj >` with `yaml2obj -o` and remove unneeded input redirection
2020-08-21 06:00:25 +08:00
# RUN: yaml2obj %s -o %t.obj
[COFF] Implement /safeseh:no and check @feat.00 flags by default Summary: Fixes PR41828. Before this, LLD always emitted SafeSEH chunks and defined __safe_se_handler_table & size. Now, /safeseh:no leaves those undefined. Additionally, we were checking for the safeseh @feat.00 flag in two places: once to emit errors, and once during safeseh table construction. The error was set up to be off by default, but safeseh is supposed to be on by default. I combined the two checks, so now LLD emits an error if an input object lacks @feat.00 and safeseh is enabled. This caused the majority of 32-bit LLD tests to fail, since many test input object files lack @feat.00 symbols. I explicitly added -safeseh:no to those tests to preserve behavior. Finally, LLD no longer sets IMAGE_DLL_CHARACTERISTICS_NO_SEH if any input file wasn't compiled for safeseh. Reviewers: mstorsjo, ruiu, thakis Reviewed By: ruiu, thakis Subscribers: llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D63570 llvm-svn: 366238
2019-07-17 02:17:33 +08:00
# RUN: lld-link -safeseh:no /out:%t.exe %t.obj /entry:main /subsystem:console
[test] Change llvm-readobj -long-option to --long-option or well-known short options. NFC Also change some options that have different semantics (cause confusion) in llvm-readelf mode: -s => -S -t => --symbols -sd => --section-data llvm-svn: 359651
2019-05-01 13:49:01 +08:00
# RUN: llvm-readobj --file-headers %t.exe | FileCheck %s
COFF: Set Load Configuration entry in Data Directory. Load Configuration field points to a structure containing information for SEH. That data strucutre is not created by the linker but provided by an external file. What we have to do is just to set __load_config_used address to the header. llvm-svn: 242427
2015-07-17 02:30:35 +08:00
COFF: Layout sections in the same order as link.exe One place where this seems to matter is to make sure the .rsrc section comes after .text. The Win32 UpdateResource() function can change the contents of .rsrc. It will move the sections that come after, but if .text gets moved, the entry point header will not get updated and the executable breaks. This was found by a test in Chromium. Differential Revision: https://reviews.llvm.org/D45260 llvm-svn: 329221
2018-04-05 03:15:55 +08:00
# CHECK: LoadConfigTableRVA: 0x2000
COFF: Set Load Configuration entry in Data Directory. Load Configuration field points to a structure containing information for SEH. That data strucutre is not created by the linker but provided by an external file. What we have to do is just to set __load_config_used address to the header. llvm-svn: 242427
2015-07-17 02:30:35 +08:00
# CHECK: LoadConfigTableSize: 0x40
[yaml2obj] Updating LLD tests to account for LLVM r273915 This removed the -format flag from yaml2obj in favor of YAML tags. llvm-svn: 273920
2016-06-28 04:17:08 +08:00
--- !COFF
COFF: Set Load Configuration entry in Data Directory. Load Configuration field points to a structure containing information for SEH. That data strucutre is not created by the linker but provided by an external file. What we have to do is just to set __load_config_used address to the header. llvm-svn: 242427
2015-07-17 02:30:35 +08:00
header:
Machine: IMAGE_FILE_MACHINE_I386
Characteristics: []
sections:
- Name: .text
Characteristics: [ IMAGE_SCN_CNT_CODE, IMAGE_SCN_MEM_EXECUTE, IMAGE_SCN_MEM_READ ]
Alignment: 4
SectionData: B82A000000C3
[COFF] Don't hard-code the load configuration size The load configuration directory is a structure whose size varies as the OS gains additional functionality. To account for this, the structure's layout begins with a size field; this allows loaders to know which fields are available. However, LLD hard-coded the sizes (112 bytes for 64-bit and 64 for 32-bit). This means that we might not inform the loader of all the pertinent fields or we might claim that there are more fields than are actually present. To correctly account for this, the size field must be loaded from the _load_config_used symbol. N.B. The COFF spec is either wrong or out of date, the load configuration directory is not correctly documented in the specification: it omits the size field. llvm-svn: 263543
2016-03-15 17:48:27 +08:00
- Name: .rdata
Characteristics: [ IMAGE_SCN_CNT_INITIALIZED_DATA, IMAGE_SCN_MEM_READ ]
Alignment: 4
SectionData: '40000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'
COFF: Set Load Configuration entry in Data Directory. Load Configuration field points to a structure containing information for SEH. That data strucutre is not created by the linker but provided by an external file. What we have to do is just to set __load_config_used address to the header. llvm-svn: 242427
2015-07-17 02:30:35 +08:00
symbols:
- Name: .text
Value: 0
SectionNumber: 1
SimpleType: IMAGE_SYM_TYPE_NULL
ComplexType: IMAGE_SYM_DTYPE_NULL
StorageClass: IMAGE_SYM_CLASS_STATIC
SectionDefinition:
Length: 6
NumberOfRelocations: 0
NumberOfLinenumbers: 0
CheckSum: 0
Number: 0
- Name: _main
Value: 0
SectionNumber: 1
SimpleType: IMAGE_SYM_TYPE_NULL
ComplexType: IMAGE_SYM_DTYPE_NULL
StorageClass: IMAGE_SYM_CLASS_EXTERNAL
[COFF] Don't hard-code the load configuration size The load configuration directory is a structure whose size varies as the OS gains additional functionality. To account for this, the structure's layout begins with a size field; this allows loaders to know which fields are available. However, LLD hard-coded the sizes (112 bytes for 64-bit and 64 for 32-bit). This means that we might not inform the loader of all the pertinent fields or we might claim that there are more fields than are actually present. To correctly account for this, the size field must be loaded from the _load_config_used symbol. N.B. The COFF spec is either wrong or out of date, the load configuration directory is not correctly documented in the specification: it omits the size field. llvm-svn: 263543
2016-03-15 17:48:27 +08:00
- Name: .rdata
Value: 0
SectionNumber: 2
SimpleType: IMAGE_SYM_TYPE_NULL
ComplexType: IMAGE_SYM_DTYPE_NULL
StorageClass: IMAGE_SYM_CLASS_STATIC
SectionDefinition:
Length: 64
NumberOfRelocations: 0
NumberOfLinenumbers: 0
CheckSum: 0
Number: 2
COFF: Set Load Configuration entry in Data Directory. Load Configuration field points to a structure containing information for SEH. That data strucutre is not created by the linker but provided by an external file. What we have to do is just to set __load_config_used address to the header. llvm-svn: 242427
2015-07-17 02:30:35 +08:00
- Name: __load_config_used
Value: 0
[COFF] Don't hard-code the load configuration size The load configuration directory is a structure whose size varies as the OS gains additional functionality. To account for this, the structure's layout begins with a size field; this allows loaders to know which fields are available. However, LLD hard-coded the sizes (112 bytes for 64-bit and 64 for 32-bit). This means that we might not inform the loader of all the pertinent fields or we might claim that there are more fields than are actually present. To correctly account for this, the size field must be loaded from the _load_config_used symbol. N.B. The COFF spec is either wrong or out of date, the load configuration directory is not correctly documented in the specification: it omits the size field. llvm-svn: 263543
2016-03-15 17:48:27 +08:00
SectionNumber: 2
COFF: Set Load Configuration entry in Data Directory. Load Configuration field points to a structure containing information for SEH. That data strucutre is not created by the linker but provided by an external file. What we have to do is just to set __load_config_used address to the header. llvm-svn: 242427
2015-07-17 02:30:35 +08:00
SimpleType: IMAGE_SYM_TYPE_NULL
ComplexType: IMAGE_SYM_DTYPE_NULL
StorageClass: IMAGE_SYM_CLASS_EXTERNAL
...