-
Notifications
You must be signed in to change notification settings - Fork 336
Do not always require GPUProgrammableStage.entryPoint #4387
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
Conversation
Previews, as seen when this build job started (de0524b): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay! LGTM but let's wait for editors to merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with a bunch of editorial nits since we're here editing this
Spec: gpuweb/gpuweb#4387 Bug: dawn:2254 Change-Id: I51c67253b095f5daf59dac378624b6bc38fe524d Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/161901 Reviewed-by: Corentin Wallez <[email protected]> Commit-Queue: Fr <[email protected]> Kokoro: Kokoro <[email protected]>
Intent to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/k_gcnAUinT0 Spec: gpuweb/gpuweb#4387 Bug: dawn:2254 Change-Id: I134e2706c5104271b7ec12aaa25f801d7ba0e0e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5057294 Reviewed-by: Corentin Wallez <[email protected]> Commit-Queue: Fr <[email protected]> Cr-Commit-Position: refs/heads/main@{#1229320}
Change references to `GPUProgrammableStage.entryPoint`, which is no longer required (gpuweb#4387), to uses of the "get the entry point" algorithm. Rather than talking about resources "statically used" by a GPUProgrammableStage, talk about resources "statically used" by a specific entry point. Use "get the entry point" as necessary to determine the relevant entry point.
Change references to `GPUProgrammableStage.entryPoint`, which is no longer required (gpuweb#4387), to uses of the "get the entry point" algorithm. Rather than talking about resources "statically used" by a GPUProgrammableStage, talk about resources "statically used" by a specific entry point. Use "get the entry point" as necessary to determine the relevant entry point.
Change references to `GPUProgrammableStage.entryPoint`, which is no longer required (gpuweb#4387), to uses of the "get the entry point" algorithm. Rather than talking about resources "statically used" by a GPUProgrammableStage, talk about resources "statically used" by a specific entry point. Use "get the entry point" as necessary to determine the relevant entry point.
Change references to `GPUProgrammableStage.entryPoint`, which is no longer required (gpuweb#4387), to uses of the "get the entry point" algorithm. Rather than talking about resources "statically used" by a GPUProgrammableStage, talk about resources "statically used" by a specific entry point. Use "get the entry point" as necessary to determine the relevant entry point.
Change references to `GPUProgrammableStage.entryPoint`, which is no longer required (#4387), to uses of the "get the entry point" algorithm. Rather than talking about resources "statically used" by a GPUProgrammableStage, talk about resources "statically used" by a specific entry point. Use "get the entry point" as necessary to determine the relevant entry point.
In an effort to move #4342 forward, this PR makes WebGPU spec not always require
GPUProgrammableStage.entryPoint
as discussed in https://github.com/gpuweb/gpuweb/wiki/GPU-Web-2023-11-08#default-entrypoints-to-shader-modules-4342-corentin-is-very-excited-about-this-tiny-addition@kainino0x Can you have a look at this?