OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

anv/pipeline: Don't look at blend state unless we have an attachment

Browse Source 
Without this, we may end up dereferencing blend before we check for
binding->index != UINT32_MAX.  However, Vulkan allows the blend state to
be NULL so long as you don't have any color attachments.  This fixes a
segfault when running The Talos Principal.

Fixes: 12f4e00b69
Cc: mesa-stable@lists.freedesktop.org
Reviewed-by: Alex Smith <asmith@feralinteractive.com>
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
This commit is contained in:
Jason Ekstrand
2018-01-17 17:10:34 -08:00
parent 8116b9170b
commit c8949e2498
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/intel/vulkan/genX_pipeline.c
View File

@@ -1351,10 +1351,10 @@ has_color_buffer_write_enabled(const struct anv_pipeline *pipeline,
if (binding->set != ANV_DESCRIPTOR_SET_COLOR_ATTACHMENTS) if (binding->set != ANV_DESCRIPTOR_SET_COLOR_ATTACHMENTS)
continue; continue;
const VkPipelineColorBlendAttachmentState *a = if (binding->index == UINT32_MAX)
&blend->pAttachments[binding->index]; continue;
if (binding->index != UINT32_MAX && a->colorWriteMask != 0) if (blend->pAttachments[binding->index].colorWriteMask != 0)
return true; return true;
} }