-
Notifications
You must be signed in to change notification settings - Fork 371
Add note to WebGPU spec explaining what limits the number of WGSL @locations. #4077
Copy link
Copy link
Open
Labels
apiWebGPU APIWebGPU APIcopyeditingPure editorial stuff (copyediting, *.bs file syntax, etc.)Pure editorial stuff (copyediting, *.bs file syntax, etc.)moved-m0-to-m1(TEMPORARY) items moved from M0 to M1 while trying to make M0 = requirements for CR(TEMPORARY) items moved from M0 to M1 while trying to make M0 = requirements for CR
Milestone
Description
The WGSL spec has a note stating "The number of available locations for an entry point is defined by the WebGPU API." But there's not a clear-cut definition of that in the WebGPU spec anywhere.
It would be helpful to have a note in the WebGPU spec that points out what the limiting factors on locations are which the WGSL spec can then in turn link to.
From the matrix chat:
kainino: it's kind of alluding to just location numbers so maxVertexAttributes, maxInterStageShaderVariables, and maxColorAttachments
but there's also that section [Brandon] linked to, maxColorAttachmentBytesPerSample, maxInterStageShaderComponents, maybe others that are in the same space of things
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
apiWebGPU APIWebGPU APIcopyeditingPure editorial stuff (copyediting, *.bs file syntax, etc.)Pure editorial stuff (copyediting, *.bs file syntax, etc.)moved-m0-to-m1(TEMPORARY) items moved from M0 to M1 while trying to make M0 = requirements for CR(TEMPORARY) items moved from M0 to M1 while trying to make M0 = requirements for CR