Contradictory VK_HUAWEI_subpass_shading with VUIDs

[Karpov-Ruslan]

VK_HUAWEI_subpass_shading gives the example of pipeline creation (I copied only the problematic part):

VkPipelineShaderStageCreateInfo subpassShadingPipelineStageCreateInfo {
  VK_STRUCTURE_TYPE_PIPELINE_SHADER_STAGE_CREATE_INFO, NULL,
  0, VK_SHADER_STAGE_SUBPASS_SHADING_BIT_HUAWEI,
  shaderModule, "main",
  &subpassShadingConstants
};

VkComputePipelineCreateInfo subpassShadingComputePipelineCreateInfo = {
  VK_STRUCTURE_TYPE_COMPUTE_PIPELINE_CREATE_INFO, &subpassShadingPipelineCreateInfo,
  0, &subpassShadingPipelineStageCreateInfo,
  pipelineLayout, basePipelineHandle, basePipelineIndex
};

As you can see, when specifying the pipeline stage, the VK_SHADER_STAGE_SUBPASS_SHADING_BIT_HUAWEI value is used.
But VUID-VkComputePipelineCreateInfo-stage-00701 says: "The stage member of stage must be VK_SHADER_STAGE_COMPUTE_BIT".
Such a contradiction leads to incorrect operation of the VVL.

I suggest changing the VUID-VkComputePipelineCreateInfo-stage-00701 to "The stage member of stage must be either VK_SHADER_STAGE_COMPUTE_BIT or VK_SHADER_STAGE_SUBPASS_SHADING_BIT_HUAWEI"

[Karpov-Ruslan]

A similar problem is also observed with VUID-VkDescriptorSetLayoutBinding-descriptorType-01510.

According to the VK_HUAWEI_subpass_shading:

A subpass shading pipeline is a pipeline with the compute pipeline ability, allowed to read values from input attachments, and only allowed to be dispatched inside a stand-alone subpass.

I suggest adding a mention of VK_SHADER_STAGE_SUBPASS_SHADING_BIT_HUAWEI to VUID-VkDescriptorSetLayoutBinding-descriptorType-01510