2017-07-19 05:26:38 +08:00
|
|
|
; RUN: llvm-dlltool -m i386:x86-64 --input-def %s --output-lib %t.a
|
2017-07-31 19:18:41 +08:00
|
|
|
; RUN: llvm-nm %t.a | FileCheck %s
|
2019-03-26 17:02:44 +08:00
|
|
|
; RUN: llvm-readobj %t.a | FileCheck -check-prefix=ARCH %s
|
2017-07-19 05:26:38 +08:00
|
|
|
|
|
|
|
LIBRARY test.dll
|
|
|
|
EXPORTS
|
|
|
|
TestFunction==AltTestFunction
|
2018-05-09 17:21:53 +08:00
|
|
|
; When creating an import library, the DLL internal function name of
|
|
|
|
; the implementation of a function isn't visible at all.
|
|
|
|
ImpLibName = Implementation
|
|
|
|
; A different import library name and implementation name can be mixed
|
|
|
|
; with exposing it via a different name in the DLL than in code.
|
|
|
|
ImpLibName2 = Implementation2 == AltTestFunction2
|
|
|
|
; The fact that a DLL export entry is a forward to a different DLL doesn't
|
|
|
|
; matter for the import library
|
|
|
|
ImpLibName3 = kernel32.Sleep
|
2017-07-19 05:26:38 +08:00
|
|
|
|
2017-07-31 19:18:41 +08:00
|
|
|
; CHECK: U AltTestFunction
|
2018-07-21 04:48:29 +08:00
|
|
|
; CHECK-NEXT: W TestFunction
|
2017-07-31 19:18:41 +08:00
|
|
|
; CHECK: U __imp_AltTestFunction
|
2018-07-21 04:48:29 +08:00
|
|
|
; CHECK-NEXT: W __imp_TestFunction
|
2018-05-09 17:21:53 +08:00
|
|
|
; CHECK: T ImpLibName
|
|
|
|
; CHECK-NEXT: T __imp_ImpLibName
|
|
|
|
; CHECK: U AltTestFunction2
|
2018-07-21 04:48:29 +08:00
|
|
|
; CHECK-NEXT: W ImpLibName2
|
2018-05-09 17:21:53 +08:00
|
|
|
; CHECK: U __imp_AltTestFunction2
|
2018-07-21 04:48:29 +08:00
|
|
|
; CHECK-NEXT: W __imp_ImpLibName2
|
2018-05-09 17:21:53 +08:00
|
|
|
; CHECK: T ImpLibName3
|
|
|
|
; CHECK-NEXT: T __imp_ImpLibName3
|
2019-03-26 17:02:44 +08:00
|
|
|
|
|
|
|
; ARCH-NOT: unknown arch
|