Fix incorrectly defined image memory barrier
authorMarcin Kańtoch <Marcin.Kantoch@amd.com>
Fri, 10 Feb 2017 09:43:52 +0000 (10:43 +0100)
committerPyry Haulos <phaulos@google.com>
Fri, 17 Feb 2017 16:28:33 +0000 (11:28 -0500)
In ResolveImageToImage::iterate() method a memory barrier is defined
to change the layout of source image. By mistake destination image
parameters are used to define subresource range. It causes validation
errors as in some cases the subresource range extends beyond
the dimensions of the source image.

The fix uses source image parameters to define the memory barrier.

Modified tests:
dEQP-VK.api.copy_and_blit.resolve_image.*

Components: Vulkan
VK-GL-CTS issue: 160

Change-Id: I0ef72fbc99b127129441b7c66b43afd7b5a1e0ef

external/vulkancts/modules/vulkan/api/vktApiCopiesAndBlittingTests.cpp

index c2886de..8b93c33 100644 (file)
@@ -3059,7 +3059,7 @@ tcu::TestStatus ResolveImageToImage::iterate (void)
                                0u,                                                                     // deUint32                             baseMipLevel;
                                1u,                                                                     // deUint32                             mipLevels;
                                0u,                                                                     // deUint32                             baseArraySlice;
-                               getArraySize(m_params.dst.image)        // deUint32                             arraySize;
+                               getArraySize(m_params.src.image)        // deUint32                             arraySize;
                        }
                },
                // destination image