Add WebGPU backend #2140
Draft
Add WebGPU backend #2140
+7,397
−202
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ile-imp-webgpu output
…s necessary. This does mean we end up simulating 32-bit max/min atomic ops with CAS loops instead of using the native wgsl versions. Worth the tradeoff for better compativbility, however.
…r limit up-front, warning has just been removed for now.
…eading from a local array in ScalarSpace, for example, 8- and 16-bit values are padded and should be accessed through direct indexing, instead of read_*/write_* functions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP WebGPU backend (#1403)
The JS glue generation is still very basic and barely enough to implement the server protocol on top of. There's also a slightly weird mixture of generating JS vs just accessing the embedded JSON manifest that I'm still hoping to clean up a bit.