tree df6f06b744b752c5549d232e165899cef222f3aa
parent 639f5461e37e386a62edb7381563b3986741b0c2
author David Neto <dneto@google.com> 1605211216 -0500
committer GitHub <noreply@github.com> 1605211216 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfrZRQCRBK7hj4Ov3rIwAAdHIIAGN44owGDMWF1jpQNiGEy/eE
 fU9F87/mMsuMrRxq4RkJbGZDygBescDJoOgCY2zyQlIU5AMoDvRwXab+fo3m9Sm3
 T1QBhsALMHc5YdKIxtcy2Tlwi25hjSc9ydzvM/EOXVhWXvxHPmCS/uZFuPsVy0SI
 BMGs6oSu3Wo37Nvue3YztKxxVGAus18JM6c3BLiOibKzL8syt3g5PcrGEmhY6NpU
 9ykTGnD9sWv0fwnou7wvM9LBLQM7M50CUHiTM5dNY9g59Nm3Y2LHNf6uRZbDqPo5
 /Swi14nDROIUJVlsKqaps/UDTzFSfQFkIEF8IZZS1+Iskc1TaeaLs4aMMDXXtuE=
 =ckgd
 -----END PGP SIGNATURE-----
 

Avoid spuriously adding Geometry capability for vert, tesc, tese (#2462)

Use of gl_Layer and gl_ViewportIndex in tessellation and vertex
shaders should not trigger the addition of the Geometry capability.

Fixes #2461

Added tests for use of gl_Layer and gl_ViewportIndex in a tessellation
evaluation shader.

Several tests for NVIDIA features for tessellation, vertex, or mesh
shaders now lose the Geometry or MultiViewport capabilities.
This is ok because the functionality is already covered by
the ShaderViewportIndexLayerNV capability.

The spv.meshShaderPerViewBuiltins.mesh test now fails validation
because the validator does not know that PrimitiveId (and possibly
other) builtins are enabled by the MeshShadingNV capability.
I filed https://github.com/KhronosGroup/SPIRV-Headers/issues/179 to
fix the grammar upstream.