Increase maxInterStageShaderComponents to 64 - #4517
Merged
Merged
Conversation
Contributor
|
Previews, as seen when this build job started (d5f1ec7): |
kainino0x
approved these changes
Mar 15, 2024
kainino0x
left a comment
Contributor
There was a problem hiding this comment.
I believe the base of 60 came from Metal, not Vulkan: "Maximum number of input components to a fragment function" per correspondence doc.
However now that we've dropped Apple3, that's not relevant anymore. LGTM
Contributor
|
Resolved in today's meeting to accept this. |
Contributor
GPU Web WG 2024-03-27 |
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
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.
Follow-up to #4503, #4509 & #1962 (comment).
We need to increase this limit to 64 since
maxInterStageShaderVariablesis 16 and the new algorithm counts each variable as 4 components.