From: Andres Rodriguez <andresx7@gmail.com>
Date: Wed, 18 Jul 2018 18:18:57 +0000 (-0400)
Subject: radv: fix wmaybe-uninitialized in radv_meta_fast_clear.c
X-Git-Tag: upstream/19.0.0~3725
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d3d9513556068093b902bff3bdd55eb0e4bccfe2;p=platform%2Fupstream%2Fmesa.git

radv: fix wmaybe-uninitialized in radv_meta_fast_clear.c

Assignment and usage of this variable both happen inside an
if(rad_image_has_dcc()) {} blocks. It seems gcc plays it safe and
assumes that both function calls could have different return values.

But in this case we should be safe.

Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
---

diff --git a/src/amd/vulkan/radv_meta_fast_clear.c b/src/amd/vulkan/radv_meta_fast_clear.c
index 932a6c9..b42a678 100644
--- a/src/amd/vulkan/radv_meta_fast_clear.c
+++ b/src/amd/vulkan/radv_meta_fast_clear.c
@@ -586,7 +586,7 @@ radv_emit_color_decompress(struct radv_cmd_buffer *cmd_buffer,
 	VkDevice device_h = radv_device_to_handle(cmd_buffer->device);
 	VkCommandBuffer cmd_buffer_h = radv_cmd_buffer_to_handle(cmd_buffer);
 	uint32_t layer_count = radv_get_layerCount(image, subresourceRange);
-	bool old_predicating;
+	bool old_predicating = false;
 	VkPipeline pipeline;
 
 	assert(cmd_buffer->queue_family_index == RADV_QUEUE_GENERAL);