-
Notifications
You must be signed in to change notification settings - Fork 321
Issues: gpuweb/gpuweb
List of issues to discuss with TC39, WASM, JS engine teams
#747
opened May 4, 2020 by
kainino0x
Open
24
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Proposal: fully explicit, non-exclusive "auto" layouts in WGSL (without createPipelineLayout)
api
WebGPU API
proposal
wgsl
WebGPU Shading Language Issues
Proposal: "auto" layout algorithm should be able to generate any layout
api
WebGPU API
proposal
wgsl
WebGPU Shading Language Issues
Hardware feature levels (and compat)
api
WebGPU API
compat
WebGPU Compatibility Mode
investigation
proposal
Define conventions/rules for features that add new limits
api
WebGPU API
needs-cts-issue
This change requires tests (or would need tests if accepted), but may not have a CTS issue filed yet
proposal
Multi-queue proposal with explicit transfers
api
WebGPU API
large
multi-queue
Part of the multi-queue feature
proposal
Strawman Multi-Queue Proposal
api
WebGPU API
large
multi-queue
Part of the multi-queue feature
proposal
Clarify the semantics of packed formats
api resolved
Resolved - waiting for a change to the API specification
api
WebGPU API
investigation
moved-m0-to-m1
(TEMPORARY) items moved from M0 to M1 while trying to make M0 = requirements for CR
proposal
ProTip!
Exclude everything labeled
bug
with -label:bug.