1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
# WebAssembly support in Swift
WebAssembly is a platform that significantly differs from hardware platforms that Swift already supports.
While it's a virtual machine, there are considerations to be taken into account when targeting it:
* WebAssembly is still at an early stage, so many features you'd be expect from other platforms are not
available yet, specifically:
1. `wasm64` variant is not specified yet, only the 32-bit `wasm32` variant is supported in WebAssembly
hosts such as browsers.
2. While a preview of multi-threading and atomics is available in some browsers and stand-alone
WebAssembly hosts, [the corresponding proposal](https://github.com/WebAssembly/threads/) haven't
formally reached the implementation phase yet.
The multi-threading feature is available in `wasm32-unknown-wasip1-threads` target, but it's not
in `wasm32-unknown-wasi` target.
3. Dynamic linking is not formally specified and tooling for it is not available yet.
* Binary size is a high priority requirement. Since WebAssembly payloads are usually served in browsers,
one wouldn't want end users to download multi-megabyte binaries.
## Building Swift SDK for WebAssembly
The [Swift SDK](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0387-cross-compilation-destinations.md)
for WebAssembly is built using the following command:
```bash
./utils/build-script --build-wasm-stdlib
```
This command will build the Swift compiler for the host platform and then build the Swift standard library
for WebAssembly targets. The resulting Swift SDK `.artifactbundle` will be placed in the `../swift-sdk-generator/Bundles`
directory.
## Building Swift SDK for WebAssembly without building the compiler
Building the Swift compiler is a time-consuming process. If you only want to build the Swift standard library
with pre-built Swift compiler, you can use the following command:
```console
$ SWIFT_TOOLS_PATH=path/to/swift-development-snapshot/usr/bin
$ ./utils/build-script \
--skip-build-llvm \
--skip-build-swift \
--skip-build-cmark \
--build-wasm-stdlib \
--native-swift-tools-path="$SWIFT_TOOLS_PATH" \
--native-clang-tools-path="$SWIFT_TOOLS_PATH" \
--native-llvm-tools-path="$SWIFT_TOOLS_PATH"
```
## Notes on the implementation
Here we're describing some decisions that were made while developing
the implementation.
### Relative Pointers
Relative pointers are used in Swift runtime, but currently it's not feasible to use them for some cases
where the pointee is a function pointer. The reason is that WebAssembly has a separate address space for
functions and data, and the offset bwtween a function and a data pointer cannot be defined. Therefore,
we have to use absolute pointers for function pointers in WebAssembly (see `include/swift/ABI/CompactFunctionPointer.h`
for more details).
|
