-
Notifications
You must be signed in to change notification settings - Fork 694
Create SIMD repo to discuss SIMD proposal? #1035
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
Comments
I do like the format in the design repo. Tables are easy to read :) |
Thanks @lukewagner. Is there a plan/need to migrate these new proposals to the main Wasm/Design repo once they mature with implementations? |
Tools like wabt can just support "extensions" IMO, without needing forks. |
A number of folks have asked about adding extensions to wabt. I agree that it would be good to support extensions w/out forks, but I'd like to make sure we can do it in a way that doesn't make it difficult to maintain. |
@arunetm Yes, I think the idea of these feature repos is that they culminate with their branch being merged into the main spec repo and the feature repo either being retired/archived or moved on to a new "v.2" branch of the feature. |
I've updated the WebAssembly mapping in the portable SIMD repo to use a single |
Please let me know ... where best to post this issue. Please consider - '...A new data type called a "posit" is designed for direct drop-in replacement for IEEE Standard 754 floats ...' From Dr. John L. Gustafson's intro: Thanks @lukewagner for all you and the WA community do. I love WebAssembly ... it enables magic like webDSP WebAssembly Video Editor! |
I created github.com/webassembly/simd, so closing out this issue. @Art This issue is scoped pretty narrowly to just the administrative task of creating a repo in which to discuss SIMD, so probably better to create a new issue for posits. |
Actually closing this issue. :-) |
People are interested in discussing what SIMD in wasm would look like, starting from the current portable-SIMD proposal. I propose creating a new github.com/webassembly/simd repo that is a fork of the spec repo which can host SIMD-scoped discussions (similar to what is being proposed for GC). Initial discussion would probably be around .md files in a new /proposals/simd subdir and could later progress to modifications to the spec text and interpreter. Make sense?
The text was updated successfully, but these errors were encountered: