mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-20 17:48:15 +02:00
3d75082c02
When we are using compute resolve, we can get values the CTS does not expect due to the value we end up writing for UNORM in `nir_image_deref_store`. Make the compute resolve rounding path match with the output of the fragment shader resolve path, by going through the same FP16 RTZ conversion as we do for UNORM/SNORM formats. This is why VK_EXT_sample_locations CTS was failing on > GFX9. On <= GFX9, I am assuming we are falling back to RESOLVE_FRAGMENT, due to DCC stuff, which is why it works there. I tested a handful of images from the Vulkan CTS for the sample locations and resolve tests for diff UNORM formats from the qpa file forcing FRAGMENT and with this change. With this change, we now match on the compute resolve path the same sha for the ones I compared with ImageMagick `identify`. CTS passes for: *resolve*, *image_clearing* and *sample_locations* on RX 7900XTX. Signed-off-by: Autumn Ashton <misyl@froggi.es> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28237> |
||
|---|---|---|
| .. | ||
| radv_meta.c | ||
| radv_meta.h | ||
| radv_meta_astc_decode.c | ||
| radv_meta_blit.c | ||
| radv_meta_blit2d.c | ||
| radv_meta_buffer.c | ||
| radv_meta_bufimage.c | ||
| radv_meta_clear.c | ||
| radv_meta_copy.c | ||
| radv_meta_copy_vrs_htile.c | ||
| radv_meta_dcc_retile.c | ||
| radv_meta_decompress.c | ||
| radv_meta_etc_decode.c | ||
| radv_meta_fast_clear.c | ||
| radv_meta_fmask_copy.c | ||
| radv_meta_fmask_expand.c | ||
| radv_meta_resolve.c | ||
| radv_meta_resolve_cs.c | ||
| radv_meta_resolve_fs.c | ||