tree 88f59aa90adcd9bb1da94a23eb0e74136b7fab60
parent c341f7a6cd441d05ca1347ee39f2f03f32225c59
author sfricke-samsung <46493288+sfricke-samsung@users.noreply.github.com> 1599069733 -0700
committer GitHub <noreply@github.com> 1599069733 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfT94lCRBK7hj4Ov3rIwAAdHIIAC7cUiSbN2w2UrCx0gg+0rdj
 +cIbFFZqiQ+Q7BZzws29PlLRHYyAi6viGpC7rsmr4Vc5o5UzyOFrP2OoV5l1yCOX
 DEf7AmBtRfA9N6+ps8SAmrQydj/bbKtJNhghmbryC2o/OSiRAnlVE1IhtUpAyrBM
 VN7Q8eCw6YL1vsx8UVogyhmqg+8i88D0ynLvxB8NFD9/RJMryzTe3Qi3DO4nR0SN
 S+dL06t8ga2udsq+qf25nKyrkv2Ohr4mGDYkoztfaCfpniR/AlQDpmVJq05RUf1k
 gr9gMRgMnZFs82qHw+8ftoBtSvhSYq6N5dIvdmCallUC08nwxbZ+OPmwNINgdPg=
 =jisk
 -----END PGP SIGNATURE-----
 

spirv-val: Add Vulkan VUID labels to BuiltIn (#3756)

The Vulkan 1.2.152 headers/spec now include Valid Usage IDs (VUID)
for every BuiltIn. This change adds labeling to help aid tracking
the coverage gap in Vulkan targeted validation. This is done with
a script in the Validation Layers that parses the source for VUID
strings, both that there is an implementation and a test for it.

There are 2 main changes:

1. A VUID string is added where applicable. It is wrapped in a function
that at runtimes checks if Vulkan is the target so that other targets
will not be effected as the output error only changes for Vulkan and
the overhead only occurs if there is an error at all.

2. For unit test, a new parameter value was added to allow make sure
that for each VUID there is a matching test. There are cases where the
same unit test checks multiple VUs via the parameter feature of gtest.
For this, I added a custom gMock Matcher to simply loop over a list
of VUID strings