这是indexloc提供的服务,不要输入任何密码
Skip to content

maxInterStageShaderComponents seems to overlap with maxInterStageShaderVariables #4688

@mwyrzykowski

Description

@mwyrzykowski

(Background: #1962)

maxInterStageShaderComponents says it is:

The maximum allowed number of components of input or output variables for inter-stage communication

However, in the validation where this limit is used:

Each user-defined output of descriptor.vertex consumes 4 scalar components.

So it is really not the number of components because a single float uses 4 components according to the validation.

For both the vertex and fragment stage, there are some places where the limit is decremented by 1 if front_facing builtin is used for instance. But in neither stage are these minus one subtractions greater than subtracting 4, so we could say if any are used then the number is decremented by 4 or 1.

But we already have maxInterStageShaderVariables, which seems to overlap with maxInterStageShaderComponents except being more appropriately named.

Do we really need two limits here when it would seem that one would suffice?

Metadata

Metadata

Assignees

Labels

apiWebGPU APIapi resolvedResolved - waiting for a change to the API specificationneeds investigationRequires an investigation into implementation constraintsneeds-cts-issueThis change requires tests (or would need tests if accepted), but may not have a CTS issue filed yetpotentially breakingCould require a breaking change to the API

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions