We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At the moment (as far as I see) the only way to extract more then one lane from a v128 value is to do the following:
(local $t v128) ... local.tee $t f32x4.extract_lane 0 local.get $t f32x4.extract_lane 1 local.get $t f32x4.extract_lane 2 local.get $t f32x4.extract_lane 3 ...
This seems quite inefficient, and clearly has a large storage footprint. I'm wondering whether there is a need of [f32x4,f64x2,...].extract_all.
[f32x4,f64x2,...].extract_all
The text was updated successfully, but these errors were encountered:
No branches or pull requests
At the moment (as far as I see) the only way to extract more then one lane from a v128 value is to do the following:
This seems quite inefficient, and clearly has a large storage footprint. I'm wondering whether there is a need of
[f32x4,f64x2,...].extract_all
.The text was updated successfully, but these errors were encountered: