Fix some CTS bugs that cause validation failures
authorPiers Daniell <pdaniell@nvidia.com>
Wed, 22 Nov 2017 20:23:12 +0000 (13:23 -0700)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Fri, 12 Jan 2018 12:32:50 +0000 (07:32 -0500)
commitea0a74f0f7a27af6c3b9234528a65851fc110cac
tree9d2ed908c6e24d77b2fc993d74e7ef570508e5cf
parentde49cb3465893751faf414c828f507b09ebe9d1c
Fix some CTS bugs that cause validation failures

Most of these are misuse of the dstStageMask parameter to
vkCmdPipelineBarrier. The dstStageMask has to be compatible
with the destination access type of the buffer or image.

The other large source of validation errors is a bug
in the CTS framework when calling vkCreateDevice. The
wrong pNext member was used for setting the enabled
features. The effect is that all features were disabled.

Affects:

dEQP-VK.pipeline.push_constant.graphics_pipeline.*
dEQP-VK.pipeline.multisample_shader_builtin.sample_mask.pattern.*
dEQP-VK.*

Components: Vulkan

VK-GL-CTS issue: 862

Change-Id: I58ca4e033d7d66b52c6726a635808b9b747546d8
(cherry picked from commit 23336be1abda90e87d9bbaf5e0398ca489f0cbc6)
external/vulkancts/modules/vulkan/pipeline/vktPipelineMultisampleBaseResolveAndPerSampleFetch.cpp
external/vulkancts/modules/vulkan/pipeline/vktPipelinePushConstantTests.cpp
external/vulkancts/modules/vulkan/vktTestCase.cpp