You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 22, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 22, 2021. It is now read-only.
The next sync meeting will be Friday, October 2 at 9:00AM - 10:00AM PDT/ 6:00PM - 7:00PM CEST). Please respond with agenda items you would like to discuss. If no agenda items are posted here 24 hours before the meeting, we will cancel.
If this meeting doesn't already appear on your calendar, or you are a new attendee, please fill out this form to attend.
Discuss #256, which makes out-of-bounds lane index immediate for instructions like replace_lane and extract_lane a parse/decode error (malformed) instead of validation error (which they currently are).
Activity
abrown commentedon Sep 4, 2020
Hopefully we can resolve the dot product discussion:
Maratyszcza commentedon Sep 21, 2020
I'd like that we decide on instruction proposals with experimental data:
i32x4.dot_i16x8_sandi32x4.dot_i16x8_add_sinstructions (i32x4.dot_i16x8_s instruction #127)v128.load32_zeroandv128.load64_zeroinstructions (v128.load32_zero and v128.load64_zero instructions #237)and decide on removing integer Not Equals instructions (#351)
ngzhian commentedon Sep 24, 2020
Discuss #256, which makes out-of-bounds lane index immediate for instructions like replace_lane and extract_lane a parse/decode error (malformed) instead of validation error (which they currently are).
tlively commentedon Sep 24, 2020
It would also be good to have a wider discussion of what to do about feature detection: #356
lars-t-hansen commentedon Sep 28, 2020
Probably also whether v128 is a number type (#363), as it affects how the SIMD proposal fits into the larger language.
tlively commentedon Oct 3, 2020
Thanks everyone! We didn't get to cover everything, but we will have our next meeting in two weeks. The calendar event should be updated, so let me know if something went wrong there. The notes from this meeting are at: https://docs.google.com/document/d/1JmdwVuQsTmP_sSwti0AV_wSFIc9Y2s8vIIeBIP8kEZ8/edit?usp=sharing