Closed Bug 1953930 Opened 7 months ago Closed 4 months ago

WebGPU pipelines should only reject missing `override`s if they're used and not specified

Categories

(Core :: Graphics: WebGPU, defect, P1)

Product:
Core
Component:
Graphics: WebGPU
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: ErichDonGubler, Assigned: aleiserson)

References

(Blocks 1 open bug)

Details

Firefox's WebGPU rejects GPU pipelines containing a shader stage where:

  1. The shader module contains overrides with no default value.
  2. The constants for the stage do not specify all overrides in the shader module in full.

In May of 2024, it was clarified by the WebGPU standard committee that the above should not be an error unless the missing override constant(s) are actually used by the entry point used in the shader stage.

Upstream tracking: wgpu#5885

Blocks: 1951217
Assignee: nobody → aleiserson
Status: NEW → ASSIGNED
Priority: -- → P1
Depends on: 1972183
No longer depends on: webgpu-update-wgpu
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.