1; RUN: llvm-dlltool -m i386:x86-64 --input-def %s --output-lib %t.a
2; RUN: llvm-nm %t.a | FileCheck %s
3; RUN: llvm-readobj %t.a | FileCheck -check-prefix=ARCH %s
4; RUN: llvm-readobj --symbols %t.a | FileCheck -check-prefix=SYMBOLS %s
5
6LIBRARY test.dll
7EXPORTS
8TestFunction==AltTestFunction
9; When creating an import library, the DLL internal function name of
10; the implementation of a function isn't visible at all.
11ImpLibName = Implementation
12; A different import library name and implementation name can be mixed
13; with exposing it via a different name in the DLL than in code.
14ImpLibName2 = Implementation2 == AltTestFunction2
15; The fact that a DLL export entry is a forward to a different DLL doesn't
16; matter for the import library
17ImpLibName3 = kernel32.Sleep
18
19; CHECK:      U AltTestFunction
20; CHECK-NEXT: W TestFunction
21; CHECK:      U __imp_AltTestFunction
22; CHECK-NEXT: W __imp_TestFunction
23; CHECK:      T ImpLibName
24; CHECK-NEXT: T __imp_ImpLibName
25; CHECK:      U AltTestFunction2
26; CHECK-NEXT: W ImpLibName2
27; CHECK:      U __imp_AltTestFunction2
28; CHECK-NEXT: W __imp_ImpLibName2
29; CHECK:      T ImpLibName3
30; CHECK-NEXT: T __imp_ImpLibName3
31
32; ARCH-NOT: unknown arch
33
34; SYMBOLS:        Symbol {
35; SYMBOLS:          Name: TestFunction
36; SYMBOLS-NEXT:     Value: 0
37; SYMBOLS-NEXT:     Section: IMAGE_SYM_UNDEFINED (0)
38; SYMBOLS-NEXT:     BaseType: Null (0x0)
39; SYMBOLS-NEXT:     ComplexType: Null (0x0)
40; SYMBOLS-NEXT:     StorageClass: WeakExternal (0x69)
41; SYMBOLS-NEXT:     AuxSymbolCount: 1
42; SYMBOLS-NEXT:     AuxWeakExternal {
43; SYMBOLS-NEXT:       Linked: AltTestFunction (2)
44; SYMBOLS-NEXT:       Search: Alias (0x3)
45; SYMBOLS-NEXT:     }
46; SYMBOLS-NEXT:   }
47