Couldn't you do something like [[builtin frag_depth, location 2]] var my_fragdepth : f32 ?

You could, but that would look rather awkward, since there is nothing to refer to the "location 2" on the API side.

@magcius doing things early is the landmark of todays explicit graphics API. We don't want to delay something to later just because we can. Shader translation may be not the most expensive part of the pipeline creation, but it's still work:

parsing
type checking
uniformity/control flow analysis
validating

Moreover, if user is creating 1000 pipelines using the same fragment shader, it would be much beneficial if the work for this fragment shader was naturally reused as a part of the GPUShaderModule building.

All in all, implementations are free to defer shader translation as well as validation, we are totally cool with that. We are not cool with the idea that this will be forced upon. We'd like to translate the shader at createShaderModule and know about their interface at that point.

As for the full-pipeline optimization, it's not clear if this is something we are going to do anyway. It might be best to leave this to the drivers.

Interface matching rules #644

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions