Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v128 question #210

Open
yamt opened this issue Jun 21, 2023 · 1 comment
Open

v128 question #210

yamt opened this issue Jun 21, 2023 · 1 comment

Comments

@yamt
Copy link
Contributor

yamt commented Jun 21, 2023

why component-level valtype doesn't have an equivalent of v128?
if it's intentionally excluded, i guess it warrants a note in the explainer.

@lukewagner
Copy link
Member

I suppose #181 could be considered a (generalized) solution to this (using, e.g., [u8;16] or [f32;4]), with tuple being a short-term workaround. The Canonical ABI would layout a list of such tuples contiguously in linear memory so that core wasm could use v128.load/v128.store directly on the incoming/outgoing lists of vectors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants