Avoid using unsupported rasterization order feature struct

Rasterization order attachment tests with explicit synchronization
mechanisms were chaining the features structure, but these tests are run
on implementations not supporting the extension.

Affected tests:
dEQP-VK.rasterization.rasterization_order_attachment_access.*

Components: Vulkan
VK-GL-CTS issue: 3617

Change-Id: Ia3d3fac2960d1588007c320ed1b92bb6160527fb

diff --git a/external/vulkancts/modules/vulkan/rasterization/vktRasterizationOrderAttachmentAccessTests.cpp b/external/vulkancts/modules/vulkan/rasterization/vktRasterizationOrderAttachmentAccessTests.cpp
index 107c401..1b4df33 100644 (file)
--- a/external/vulkancts/modules/vulkan/rasterization/vktRasterizationOrderAttachmentAccessTests.cpp
+++ b/external/vulkancts/modules/vulkan/rasterization/vktRasterizationOrderAttachmentAccessTests.cpp
@@ -798,7 +798,7 @@ void AttachmentAccessOrderTestCase::checkSupport (Context& context) const
        const auto      physicalDevice  = context.getPhysicalDevice();
 
        VkPhysicalDeviceRasterizationOrderAttachmentAccessFeaturesARM   rasterizationAccess     = initVulkanStructure();
-       VkPhysicalDeviceFeatures2                                                                               features2                       = initVulkanStructure(&rasterizationAccess);
+       VkPhysicalDeviceFeatures2                                                                               features2                       = initVulkanStructure(m_explicitSync ? nullptr : &rasterizationAccess);
 
        vki.getPhysicalDeviceFeatures2(physicalDevice, &features2);