llvm-project/lld/test/pecoff/exportlib2.test

# RUN: yaml2obj %p/Inputs/export.obj.yaml > %t.obj
#
# RUN: lld -flavor link /out:%t.dll /dll /entry:init \
# RUN:   /export:exportfn1 /export:exportfn2 /lldmoduledeffile:%t.def -- %t.obj
# RUN: FileCheck %s < %t.def

CHECK: LIBRARY "exportlib2.test.tmp.dll"
CHECK: EXPORTS
CHECK:   exportfn1 @1
CHECK:   exportfn2 @2
CHECK:   exportfn3@256 @3
[PECOFF] Add a test for lib.exe subcommand. Previously the input file for the lib.exe command would be removed as soon as the command exits, so we couldn't write a test to check the file contents are correct. This patch adds /lldmoduledeffile: option to retain a copy of the temporary file at the given file path, so that you can see the file if you want. llvm-svn: 207727 2014-05-01 08:06:56 +08:00			`# RUN: yaml2obj %p/Inputs/export.obj.yaml > %t.obj`
			`#`
			`# RUN: lld -flavor link /out:%t.dll /dll /entry:init \`
			`# RUN: /export:exportfn1 /export:exportfn2 /lldmoduledeffile:%t.def -- %t.obj`
			`# RUN: FileCheck %s < %t.def`

			`CHECK: LIBRARY "exportlib2.test.tmp.dll"`
			`CHECK: EXPORTS`
			`CHECK: exportfn1 @1`
[PECOFF] Resolve dllexported symbols. We did not actively try to resolve dllexported symbols specified by /export or by a module definition file. So if exported symbols would be resolved for other reasons, like other symbols refer to them, that was fine, but if (unreferenced) exported symbols were in an archive file, and no one refers to that file in the archive, they remained unresolved. That would obviously cause the issue that dllexported symbols are not in a resultant DLL. In this patch, we create an undefined symbol for each dllexported symbol, to let the core linker to resolve it. llvm-svn: 208452 2014-05-10 06:19:49 +08:00			`CHECK: exportfn2 @2`
			`CHECK: exportfn3@256 @3`