Had a meeting with @arunetm where we discussed the TAG review, and how we review and what we expect. We really would like a better explainer, geared toward landing the feature as part of the broader Web Paltform. The current one is really technical and written for the WASM CG and differs somewhat from what we are expecting. Please read our explainer about explainers: https://w3ctag.github.io/explainers For instance we would like a section about Considered Alternatives, which should list the SIMD.js work and why that was abandoned. We would also like information about whether it would be possible to bring SIMD to JavaScript in the future so that WASM and JS don't diverge too much. Or whether that might not make sense. Are there any current outstanding issues or disagreement that we should know about? Is the proposal playing favors to some architectures or making sure that design is done in a way that different architectures can gain similar performance with optimized pipelines? What is the plan for > 128 SIMD? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/487#issuecomment-611175926
Received on Wednesday, 8 April 2020 20:27:08 UTC