tree b39b63d59b61a3d416b81227a021584855ca7f40
parent b8b9eb8640c8c0107ba580fbcb10f969022ca32c
author David Neto <dneto@google.com> 1692805334 -0400
committer GitHub <noreply@github.com> 1692805334 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJk5ijWCRBK7hj4Ov3rIwAA3OIIAK6E9QMLA6tquWbsOJME4pO8
 r90CsZsed6rMRBBWxXow5qNm5IMjJYxp4JxlYPZj+Xb2GQ2y3ZKuYhadxxKluasG
 cXKZDGNAYOCPMjk//Vk2bb/jXY38bmtlFFVjHq3CBZID/7iwF6/Wo8qJPBofovu5
 ZVk67+gnYXxHHGglSdyb/WLV/n0d+cqC7OVGNCh7kFPw4Kkfo2x5P4OrCpBZc8e7
 1ZyG6uv+HHn6TShZTGgCDtw10WtBWfXVKtkSk3Beq1F7b3a5B54L73+QXcOQBO0F
 kPlvHyQRuWVxtt3lPLhbLn8DLUHMerI86HwuSH43VXAcPeznt6097KV9iwbez+k=
 =sfVQ
 -----END PGP SIGNATURE-----
 

Validate enums have sensible versions and are visible (#369)

* Validate enums have a sensible versions and are visible

Add version field for each eumerant.

For capabilities and instructions introduced by an extension (its
first version is "None"):
- the capability should be guarded by an extension
- the instruction should be guarded by a capability.

Other enums are presumed guarded transitiviely by use as an operand
to an instruction or another operand.

Fixes: #278, #368

* Fix capability logic, and check more cases

For capabilities, only check for lack of an extension.
If capability X lists capabilities Y and Z, those are not guards *for*
X, but rather when X is enabled it also implicitly enables Y and Z.

Also, an instruction that is *not* in a core SPIR-V version
must not be directly enabled by *both* and extension and a capability.
There are 78 existing cases that break this rule, so grandparent them
in with an allow-list.

* Add "version": "None" to enums added for a recent extension

Add it for the HostAccessQualifier enums from
SPV_INTEL_global_variable_host_access