# wasm: get self-hosted compiling, and supporting \`separate_thread\` · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/c0df70706695a67089d4e691d3d3a0f77b90298f)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: c0df70706695a67089d4e691d3d3a0f77b90298f

Requested commit: c0df70706695a67089d4e691d3d3a0f77b90298f

Commit: c0df70706695a67089d4e691d3d3a0f77b90298f

Tree: cc05dafeb6b079455c95be905761f08982a1c6fa

Author: mlugg

Committer: mlugg

## Message

```
wasm: get self-hosted compiling, and supporting `separate_thread`

My original goal here was just to get the self-hosted Wasm backend
compiling again after the pipeline change, but it turned out that from
there it was pretty simple to entirely eliminate the shared state
between `codegen.wasm` and `link.Wasm`. As such, this commit not only
fixes the backend, but makes it the second backend (after CBE) to
support the new 1:N:1 threading model.

```

## Parents

- [5ab307cf47b1f0418d9ed4ab56df6fb798305c20](https://git.cafe/gitcafe/zig/commit/5ab307cf47b1f0418d9ed4ab56df6fb798305c20?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/c0df70706695a67089d4e691d3d3a0f77b90298f?format=markdown)