-
Notifications
You must be signed in to change notification settings - Fork 909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Naga specific WGSL extensions #4410
Comments
So the idea is, to use some extension, you have to add the bit to |
|
naga_ext_push_constants
push_constant
Address Spacenaga_ext_f64
f64
typenaga_ext_early_depth_test
@early_depth_test
attributenaga_ext_multiview
(ornaga_ext_view_index
?)@builtin(view_index)
builtinnaga_ext_primitive_index
@builtin(primitive_index)
builtinnaga_ext_binding_array
(this will end up having 8Capabilities
see Updatebinding_array
relatedCapabilities
#4407)binding_array
typeAll of these have their own Capabilities therefore the validator is already aware of those non-standard items but I think we should still have our own set of extensions so that it's obvious when a shader uses those items.
Introducing a
strict_extensions: bool
field for theParser
will limit the extensions to only those defined by the spec (for now onlyf16
).Relevant errors should be different based on the
strict_extensions
field. Example: using anf64
type withstrict_extensions: true
should yield an error that informs the user that there is no such type; on the other hand, ifstrict_extensions
werefalse
, the error should inform the user that thenaga_ext_f64
extension is required.The text was updated successfully, but these errors were encountered: