Merge branch 'memory-barrier-fix' into 'vulkan-cts-1.0'
authorPyry Haulos <phaulos@google.com>
Mon, 22 Feb 2016 17:35:10 +0000 (12:35 -0500)
committerPyry Haulos <phaulos@google.com>
Mon, 22 Feb 2016 17:35:10 +0000 (12:35 -0500)
commitbaf5a69a3de4911c18c2e377a91ae5869e9dca5c
treed67dea7d73eade623927ed8cccf7c47e0ef6f801
parentdac8ac03fd97017ded62c9fa2a67294da0b0dec1
parentd31a4bbb054d4daf653208fef37f59dfdd92e864
Merge branch 'memory-barrier-fix' into 'vulkan-cts-1.0'

Fix issues with memory barrier tests.

There are multiple issues currently in the dEQP-VK.memory.pipeline_barrier.* tests.

I found 3 ocasions where the values provided to srcAccessMask and dstAccessMask are the other way around.
In particular, after a transfer operation the barrier responsible for flushing the output of the transfer writes uses srcAccessMask=0 and dstAccessMask=VK_ACCESS_TRANSFER_WRITE_BIT, when actually VK_ACCESS_TRANSFER_WRITE_BIT should have been set in srcAccessMask not in dstAccessMask.

See merge request !421
external/vulkancts/modules/vulkan/memory/vktMemoryPipelineBarrierTests.cpp