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

anv: Don't claim the null RT as a valid color target

Browse Source 
If it's NULL, we can let the compiler go ahead and delete it or flag it
as NULL.

Reviewed-by: Rafael Antognolli <rafael.antognolli@intel.com>
This commit is contained in:
Jason Ekstrand
2019-10-30 15:53:11 -05:00
parent df7a730b4f
commit c765e2156a
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/intel/vulkan/anv_pipeline.c
View File

@@ -1008,6 +1008,12 @@ anv_pipeline_link_fs(const struct brw_compiler *compiler,
if (deleted_output)
nir_fixup_deref_modes(stage->nir);
/* Now that we've determined the actual number of render targets, adjust
* the key accordingly.
*/
stage->key.wm.nr_color_regions = num_rts;
stage->key.wm.color_outputs_valid = (1 << num_rts) - 1;
if (num_rts == 0) {
/* If we have no render targets, we need a null render target */
rt_bindings[0] = (struct anv_pipeline_binding) {
@@ -1018,12 +1024,6 @@ anv_pipeline_link_fs(const struct brw_compiler *compiler,
num_rts = 1;
}
/* Now that we've determined the actual number of render targets, adjust
* the key accordingly.
*/
stage->key.wm.nr_color_regions = num_rts;
stage->key.wm.color_outputs_valid = (1 << num_rts) - 1;
assert(num_rts <= max_rt);
assert(stage->bind_map.surface_count == 0);
typed_memcpy(stage->bind_map.surface_to_descriptor,