diff options
author | Jason Ekstrand <[email protected]> | 2016-03-08 11:19:02 -0800 |
---|---|---|
committer | Jason Ekstrand <[email protected]> | 2016-03-08 15:40:11 -0800 |
commit | bbbdd32c192a350dd63f21cf0b01a30ee6a085ff (patch) | |
tree | 67495b82c82b1298bf346910a570eb9c6b5f9b36 /src | |
parent | dc504a51fb47d1b4a12011cb1986c3897fad007f (diff) |
anv/meta_clear: Use repclear again
Diffstat (limited to 'src')
-rw-r--r-- | src/intel/vulkan/anv_meta_clear.c | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/src/intel/vulkan/anv_meta_clear.c b/src/intel/vulkan/anv_meta_clear.c index bce94460844..a24e59950be 100644 --- a/src/intel/vulkan/anv_meta_clear.c +++ b/src/intel/vulkan/anv_meta_clear.c @@ -297,14 +297,15 @@ create_color_pipeline(struct anv_device *device, .pAttachments = blend_attachment_state }; - /* Disable repclear because we do not want the compiler to replace the - * shader. We need the shader to write to the specified color attachment, - * but the repclear shader writes to all color attachments. + /* Use the repclear shader. Since the NIR shader we are providing has + * exactly one output, that output will get compacted down to binding + * table entry 0. The hard-coded repclear shader is then exactly what + * we want regardless of what attachment we are actually clearing. */ return create_pipeline(device, samples, vs_nir, fs_nir, &vi_state, &ds_state, &cb_state, &device->meta_state.alloc, - /*use_repclear*/ false, pipeline); + /*use_repclear*/ true, pipeline); } static void |