[6.2] Allow linking _Concurrency
for WASI with Embedded Swift
#1865
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of #1863.
Explanation: Currently, when building packages for WASI with Embedded Swift, libraries such as
libswift_Concurrency.a
andlibswift_ConcurrencyDefaultExecutor.a
are not discoverable and require passing-Xlinker <swift-sdk-path>/usr/lib/swift/embedded/wasm32-unknown-wasip1
option manually. This path can be inferred by the driver, which simplifies build invocations for users significantly, while the rest of linkage options (-lswift_Concurrency
etc) can be specified in toolset files.Scope: Limited to Embedded Swift for Wasm.
Risk: Low due to limited scope.
Testing: Added new automated test cases.
Issue: rdar://148820885
Reviewer: @kateinoigakukun