With hasvk gen9+ is normal for anvil, hasvk needs old comments gen8+ of anvil

[stefano2734]

anvil is new for skylake gen 9+.

development of anvil starts for broadwell gen8 and skylake gen9.
broadwell gen 8 is here conformant for Vulkan 1.0.
Ivy bridge Gen 7 and Haswell gen 7.5 are long experimental, but why HasVK, if no Vulkan 1.0.

So comments gen 8+ and gen 9+ in anvil are with new hasvk for gen 7, 7.5 and gen 8 unnecessary.

but in hasvk this comments with gen8 are necessary because Ivy Bridge is gen 7, Haswell is gen 7.5 and Broadwell is gen 8.

three comments in anvil are false or not right in place.
16-bit storage in Vulkan 1.1 is with comment gen 8+, but not available for hasvk with broadwell gen 8.
This is not logical.

2 comments in Vulkan 1.3 are not done with gen9+ for Anvil, while hasvk with gen 7, 7.5 and 8 is here not available. But in new view with hasvk the comments in Vulkan 1.3 are right.

in optional extensions:
Performance query gen8+ in anvil, but not available in hasvk for broadwell gen 8 with a comment gen 8.
This is not logic with hasvk for gen 7, 7.5 and 8.

So there is room for improvement and more precision here.
So about 10 fields or more in anvil and HasVK are not right and without or too many comments.

The same problem was here with iris and crocus. This was solved.

[stefano2734]

Solved for anvil comments gen8+ and gen9+.
but not for HasVK.
Some features are only for gen8+ like in anvil before.
hasVK is conformant to Vulkan 1.0, but perhaps not for all hardware.
Broadwell equal gen8 was first target to Vulkan 1.0 for anvil development years before.

I see this is done at crocus with comment gen6+, gen7+ and gen7.5+, so doing this at hasvk should be possible. Information is in older versions of Mesa 23 with gen8+ comments in anvil.