Browser-native compute matured sharply this year, with workgroup memory limits
raised across all three major engines and a common subset finally shipping by
default.12
Independent benchmarks recorded a median 3.1× throughput gain on fused kernels
against the 2024 baseline, holding across discrete and integrated hardware.07
Adoption stayed gated by driver parity on mobile, where two vendors still trail the
specification by a full release and expose only a reduced feature set.23 31
Japanese conformance testing surfaced a regression that no English-language source
reported — モバイルGPUドライバの適合性に回帰が確認された —
filed against two shipping driver builds.23
German trade press put the driver gap at two release cycles, which the vendors have
not disputed publicly, though neither has committed to a date.44
Chinese developer forums report the same regression reproducing on three mid-range
chipsets, with a workaround that costs roughly 18% of the gain.52
Patent filings from one vendor describe a scheduler change that would close the gap,
but the filing carries no ship signal.61
Where the record is thin, the report says so instead of filling the gap: no source we
could verify reports shipped hardware using the new limits in production.08
Some teams report much larger gains.
could not be verified · dropped
Arrived from the sweep0 / 0
12
GPU for the Web — working note
w3.org · EN · standards body
07
Cross-engine kernel benchmark suite
arxiv.org · EN · university
23
モバイルGPUドライバ適合性レポート
techblog.jp · JA → EN · company
31
Driver parity tracker, Q3
ieee.org · EN · standards body
44
GPU-Treiber Konformität
heise.de · DE → EN · press
