Wasmtime GitHub notifications bot (Sep 12 2023 at 23:44): Wasmtime GitHub notifications bot (Sep 12 2023 at 23:44):github-actions[bot] commented on issue #7010:
Subscribe to Label Action
cc @fitzgen, @peterhuene
<details>
This issue or pull request has been labeled: "fuzzing", "wasmtime:api", "wasmtime:c-api"Thus the following users have been cc'd because of the following labels:
- fitzgen: fuzzing
- 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 13 2023 at 22:19):alexcrichton commented on issue #7010:
I should also mention before I forget, it is theoretically possible to support v128 on all platforms. We are in control of our own ABI and we could say that the v128 type always maps to memory or a pair of u64 values. This would require rejiggering not only the Cranelift trampolines generated but additionally the
WasmTytrait and how arguments are passed in the ABI. I figured that was a big lift for now where it'd be "much easier" to wait for Rust to add stable support for vector types on s390x and RISC-V in theory (in the assumption that users desiring that will coincide with a much later date in the future)
Last updated: Oct 23 2024 at 20:03 UTC