incorrect code generation for modules on Windows

[compnerd]

Is it reproducible with SwiftPM command-line tools: swift build, swift test, swift package etc?

• Confirmed reproduction steps with SwiftPM CLI. The description text must include reproduction steps with either of command-line SwiftPM commands, swift build, swift test, swift package etc.

Description

When building swift-driver on Windows with the static standard library (i.e. swift build -Xswiftc -static-stdlib -Xbuild-tools-swiftc -static-stdlib, we see a number of LNK4217 issues.

Expected behavior

No response

Actual behavior

No response

Steps to reproduce

No response

Swift Package Manager version/commit hash

No response

Swift & OS version (output of swift --version ; uname -a)

No response

[dschaefer2]

I see LNK4217 warnings all the time building SwiftPM. I think our strategy for swift build will address this.

[compnerd]

FWIW, this actively blocks building swift-driver with SPM.