Stream: git-wasmtime

Topic: wasmtime / issue #3355 Use rsix to make system calls in W...

Wasmtime GitHub notifications bot (Sep 15 2021 at 23:37):

github-actions[bot] commented on issue #3355:

Subscribe to Label Action

cc @kubkon, @peterhuene

<details>
This issue or pull request has been labeled: "cranelift", "wasi", "wasmtime:api", "wasmtime:c-api"

Thus the following users have been cc'd because of the following labels:

• kubkon: wasi
• peterhuene: wasmtime:api, wasmtime:c-api

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

Wasmtime GitHub notifications bot (Sep 16 2021 at 11:15):

akirilov-arm commented on issue #3355:

@sunfishcode Interesting, in order to fix issue #3310 on AArch64 Linux, we will need to call the membarrier(MEMBARRIER_CMD_PRIVATE_EXPEDITED_SYNC_CORE, 0), and I suppose that would have to go through rsix as well - is it implemented in the crate and if not, are there plans to? Currently, the idea is to wait for support in libc, but doing it in rsix might be a faster route.

Wasmtime GitHub notifications bot (Sep 16 2021 at 11:17):

akirilov-arm edited a comment on issue #3355:

@sunfishcode Interesting, in order to fix issue #3310 on AArch64 Linux, we need to do the membarrier(MEMBARRIER_CMD_PRIVATE_EXPEDITED_SYNC_CORE, 0) system call, and I suppose that would have to go through rsix as well - is it implemented in the crate and if not, are there plans to? Currently the idea is to wait for support in libc, but doing it in rsix might be a faster route.

Wasmtime GitHub notifications bot (Sep 16 2021 at 11:19):

bjorn3 commented on issue #3355:

Adding it to rsix would require first adding it to libc I think as rsix falls back to libc when --cfg rsix_use_libc is used.

Last updated: Oct 23 2024 at 20:03 UTC