swift-wasm-5.10-SNAPSHOT-2023-11-08-a

[lit] Repair tests for stdlib-only build

`config.host_triple` can be None when no host tools are built

This is based on 21d57e887ad1f2d319b8e89af90d2732d50ecf55 in main branch

swift-wasm-5.10-SNAPSHOT-2023-11-05-a

[lit] Repair tests for stdlib-only build

`config.host_triple` can be None when no host tools are built

This is based on 21d57e887ad1f2d319b8e89af90d2732d50ecf55 in main branch

swift-wasm-DEVELOPMENT-SNAPSHOT-2023-11-01-a

Fix calling convention mismatch for debugger utility functions

This is the 3rd attempt to fix the mismatch, where the actual definition
(e.g. `swift_retainCount`) are defined with C calling-convention and the
callers wrongly expect Swift calling-convention.

The 1st fix broke ABI compatibility by introducing new symbol references
from app-side without any availability checks.
The 2nd fix broke lldb's retain counting feature due to new x-ref to
Clang module in serialized function body by `@_alwaysEmitIntoClient`.

This attemps to avoid introducing serialized x-ref to Clang module by
using new `@extern(c)` attribute.

Co-authored-by: Karoy Lorentey <[email protected]>

swift-wasm-5.9-SNAPSHOT-2023-11-01-a

[lit] Repair tests for stdlib-only build

`config.host_triple` can be None when no host tools are built

This is based on 21d57e887ad1f2d319b8e89af90d2732d50ecf55 in main branch

swift-wasm-5.10-SNAPSHOT-2023-11-03-a

[lit] Repair tests for stdlib-only build

`config.host_triple` can be None when no host tools are built

This is based on 21d57e887ad1f2d319b8e89af90d2732d50ecf55 in main branch

swift-wasm-5.10-SNAPSHOT-2023-11-02-a

[lit] Repair tests for stdlib-only build

`config.host_triple` can be None when no host tools are built

This is based on 21d57e887ad1f2d319b8e89af90d2732d50ecf55 in main branch

swift-wasm-DEVELOPMENT-SNAPSHOT-2023-08-07-a

[installer] Do not follow an existing symbolic link when overwriting

Without `-h` option, `ln` command makes a symbolic link under the existing
link destination like `Toolchains/swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain/`.

```
$ ln -fs swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain swift-latest.xctoolchain
$ ln -fs swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain swift-latest.xctoolchain
$ tree
|-- swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain
|   |-- swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain -> swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain
|-- swift-DEVELOPMENT-SNAPSHOT-YY.xctoolchain
|-- swift-latest.xctoolchain -> swift-DEVELOPMENT-SNAPSHOT-XX.xctoolchain
```

So we should not follow the existing symbolic link even if it already
exists.

swift-wasm-5.9-SNAPSHOT-2023-08-06-a

[test] Make KeyPath test pointer-size agnostic part 2

swift-wasm-5.9-SNAPSHOT-2023-08-01-a

[test] Make KeyPath test pointer-size agnostic part 2

swift-wasm-5.9-SNAPSHOT-2023-07-28-a

[test] Make KeyPath test pointer-size agnostic part 2