LGTM2 On Wednesday, September 23, 2026 at 8:20:38 AM UTC-7 Vladimir Levin wrote:
> LGTM1 > > On Monday, September 21, 2026 at 5:43:54 PM UTC-4 Chromestatus wrote: > >> *Contact emails* >> [email protected], [email protected] >> >> *Explainer* >> https://github.com/gpuweb/gpuweb/issues/5071 >> >> *Specification* >> https://www.w3.org/TR/webgpu/#dom-gpufeaturename-atomic-vec2u-min-max >> >> *Summary* >> Allows the use of 64-bit atomic minimum and maximum operations on >> `atomic<vec2u>` in WGSL. This provides WebGPU shader authors with a way to >> implement certain algorithms that use 64-bit atomics without requiring full >> support for 64-bit integers. >> >> *Blink component* >> Blink>WebGPU >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EWebGPU%22> >> >> *Web Feature ID* >> webgpu <https://webstatus.dev/features/webgpu> >> >> *Motivation* >> This provides WebGPU shader authors with a way to implement certain >> algorithms that use 64-bit atomics without requiring full support for >> 64-bit integers. Not every device that supports 64-bit atomics can support >> every atomic operation on these types, so this feature is scoped to the min >> and max operations to deliver broadest reach. >> >> *Initial public proposal* >> https://github.com/gpuweb/gpuweb/blob/main/proposals/atomic-64-min-max.md >> >> *TAG review* >> *No information provided* >> >> *TAG review status* >> Not applicable >> >> *Goals for experimentation* >> None >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> This feature has been approved in W3C GPU for the Web WG meetings >> including participants from Safari and Firefox. >> https://github.com/gpuweb/gpuweb/wiki/GPU-Web-2026%E2%80%9009%E2%80%9015-WGSL#add-limited-support-for-64-bit-atomics-5071 >> >> >> *Gecko*: No signal (https://github.com/gpuweb/gpuweb/pull/5610) Feedback >> indicated via WebGPU standardization process. >> >> *WebKit*: Positive (https://github.com/gpuweb/gpuweb/pull/5610) >> Specification >> approval constitutes a positive signal, per >> https://github.com/WebKit/standards-positions/issues/294#issuecomment-1877411933 >> >> *Web developers*: Positive ( >> https://github.com/gpuweb/gpuweb/issues/5071#issuecomment-2660636760) >> >> *Other signals*: >> >> *WebView application risks* >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> *No information provided* >> >> >> *Debuggability* >> *No information provided* >> >> *Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?* >> Yes >> All platforms have support, where hardware support is available. >> >> *Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >> Yes >> 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. While the CTS can be embedded in WPT, the WebGPU team opted to >> keep it separate in Chromium testing to use a customized harness for >> robustness and performance. Tests added here: >> https://github.com/gpuweb/cts/pull/4662 >> >> *Flag name on about://flags* >> *No information provided* >> >> *Finch feature name* >> WebGPU >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Tracking bug* >> https://crbug.com/453689550 >> >> *Estimated milestones* >> Shipping on desktop 156 >> DevTrial on desktop 155 >> Shipping on Android 156 >> DevTrial on Android 155 >> Shipping on WebView 156 >> >> *Anticipated spec changes* >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> *No information provided* >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/4882016087703552?gate=5204891327922176 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com>. >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f87e1bec-53eb-4724-ade4-08fc7cfdf86an%40chromium.org.
