Fix VkCmdImageBlit usage in blitting tests
authorAlexander Galazin <alexander.galazin@arm.com>
Thu, 12 Jan 2017 11:53:30 +0000 (12:53 +0100)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Thu, 12 Jan 2017 13:28:43 +0000 (08:28 -0500)
Some tests call VkCmdImageBlit with a 2D destination image and a region
with dstOffset[0].z=1, dstOffset[1].z=0.

The spec says that it should be the opposite.

Affects:
dEQP-VK.api.copy_and_blit.blit_image.simple_tests.mirror_xy_nearest
dEQP-VK.api.copy_and_blit.blit_image.simple_tests.mirror_y_nearest

Components: Vulkan

Fixes Vulkancts issue: #576

Change-Id: Iaa05f3b38cd46c39d313bd044b37535c112b77dd

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

index 860f5fb..aa438b9 100644 (file)
@@ -4162,8 +4162,8 @@ tcu::TestCaseGroup* createCopiesAndBlittingTests (tcu::TestContext& testCtx)
 
                                defaultSourceLayer,     // VkImageSubresourceLayers     dstSubresource;
                                {
-                                       {defaultSize, defaultSize, 1},
-                                       {0, 0, 0}
+                                       {defaultSize, defaultSize, 0},
+                                       {0, 0, 1}
                                }                                       // VkOffset3D                           dstOffset[2];
                        };
 
@@ -4292,8 +4292,8 @@ tcu::TestCaseGroup* createCopiesAndBlittingTests (tcu::TestContext& testCtx)
 
                                defaultSourceLayer,     // VkImageSubresourceLayers     dstSubresource;
                                {
-                                       {0, defaultSize, 1},
-                                       {defaultSize, 0, 0}
+                                       {0, defaultSize, 0},
+                                       {defaultSize, 0, 1}
                                }                                       // VkOffset3D                           dstOffset[2];
                        };