WebGPU default entry points to shader modules

Category: Graphics
Type: Chromium catches up
Status: Enabled by default (Chrome 121)
Intent stage: None

Breaking change: No
Enterprise impact: None
Spec maturity: Unknown status
Web Platform Tests: Yes

WPT details: WebGPU/WGSL have a conformance test suite (https://github.com/gpuweb/cts) that is regularly pulled into Chromium and part of the testing of Dawn/Tint in Chromium.

Summary

WebGPU now allows developers to omit entry points to shader modules when creating a pipeline, improving ergonomics. If no default entry point is found, a GPUValidationError will be triggered as usual.

Standards & signals

Specification: https://gpuweb.github.io/gpuweb/#abstract-opdef-validating-gpuprogrammablestage
Firefox: Positive
Safari: Closed Without a Position
Web developers: Positive
Tracking bug: https://bugs.chromium.org/p/dawn/issues/detail?id=2254

Ecosystem

Web Platform Tests: https://wpt.fyi/results/?q=webgpu%2FWGSL
Chrome Platform Showcase: https://chrome-platform-showcase.paulkinlan-ea.deno.net/features
GenDN reference: https://gendn.paulkinlan-ea.deno.net/features
chrome.dev demos search: https://www.google.com/search?q=site%3Achrome.dev+WebGPU%20default%20entry%20points%20to%20shader%20modules
MDN Web Docs: https://developer.mozilla.org/en-US/search?q=WebGPU%20default%20entry%20points%20to%20shader%20modules
Baseline status: https://webstatus.dev/?q=WebGPU%20default%20entry%20points%20to%20shader%20modules

View on chromestatus.com