Fix using VK_EXT_provoking_vertex with VVL

Vulkan Validation Layers (VVL) automatically rejects and removes any unknown pNext pointer in an pNext chain submitted to the driver. For this purpose, a mechanism was introduced by VVL in order to allow ANGLE to allow some of our custom pNext entries to go through VVL without being removed. This had been used for only 1 of the 3 entries in the VK_EXT_provoking_vertex extension, causing it to be properly exposed, but impossible to use. This CL corrects this by adding the missing entries. Bug: angleproject:5902 Change-Id: If6478b3aa776513b92420736fa1216b014320b02 Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2854815Reviewed-by: Jamie Madill <jmadill@chromium.org> Reviewed-by: Cody Northrop <cnorthrop@google.com> Commit-Queue: Alexis Hétu <sugoi@chromium.org>

Fix using VK_EXT_provoking_vertex with VVL
c02d5f12 · Alexis Hetu · Commit Bot · 6505a768 · c02d5f12
Commit c02d5f12 authored Apr 27, 2021 by Alexis Hetu Committed by Commit Bot Apr 27, 2021
Hide whitespace changes
Inline Side-by-side

Showing with 6 additions and 0 deletions

vulkan_icd.cpp src/common/vulkan/vulkan_icd.cpp +6 -0

No files found.
--- a/src/common/vulkan/vulkan_icd.cpp
+++ b/src/common/vulkan/vulkan_icd.cpp
@@ -223,6 +223,12 @@ bool ScopedVkLoaderEnvironment::setCustomExtensionsEnvironment()

        {VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PROVOKING_VERTEX_FEATURES_EXT,
         sizeof(VkPhysicalDeviceProvokingVertexFeaturesEXT)},
+
+        {VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_PROVOKING_VERTEX_PROPERTIES_EXT,
+         sizeof(VkPhysicalDeviceProvokingVertexPropertiesEXT)},
+
+        {VK_STRUCTURE_TYPE_PIPELINE_RASTERIZATION_PROVOKING_VERTEX_STATE_CREATE_INFO_EXT,
+         sizeof(VkPipelineRasterizationProvokingVertexStateCreateInfoEXT)},
    };

    mPreviousCustomExtensionsEnv = angle::GetEnvironmentVar(kValidationLayersCustomSTypeListEnv);