From: Mark Adams <marka@nvidia.com>
Date: Fri, 15 Jan 2016 22:02:39 +0000 (-0500)
Subject: Fix offset parameter for flushMappedMemoryRange
X-Git-Tag: upstream/0.1.0~812^2~131^2~5^2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=9931d9632ce1e900213ddd41ebd25a36cc93536e;p=platform%2Fupstream%2FVK-GL-CTS.git

Fix offset parameter for flushMappedMemoryRange

In ShaderRenderCaseInstance::uploadImage2D(), the allocation object was
being passed in instead of the offset. This resulted in attempting to
flush an invalid memory range.
---

diff --git a/external/vulkancts/modules/vulkan/shaderrender/vktShaderRender.cpp b/external/vulkancts/modules/vulkan/shaderrender/vktShaderRender.cpp
index 93562a9..d45942f 100644
--- a/external/vulkancts/modules/vulkan/shaderrender/vktShaderRender.cpp
+++ b/external/vulkancts/modules/vulkan/shaderrender/vktShaderRender.cpp
@@ -813,7 +813,7 @@ de::MovePtr<Allocation> ShaderRenderCaseInstance::uploadImage2D (const tcu::Text
 
 	tcu::copy(destAccess, access);
 
-	flushMappedMemoryRange(vk, vkDevice, allocation->getMemory(), allocation, layout.size);
+	flushMappedMemoryRange(vk, vkDevice, allocation->getMemory(), allocation->getOffset(), layout.size);
 
 	return allocation;
 }