Re: [Mesa-dev] [PATCH 4/4] radv/gfx10: do not always execute a barrier before the second shader

r-b On Thu, Jul 18, 2019 at 10:04 AM Samuel Pitoiset wrote: > > > On 7/18/19 2:29 AM, Bas Nieuwenhuizen wrote: > > On Wed, Jul 17, 2019 at 3:44 PM Samuel Pitoiset > > wrote: > >> With NGG, empty waves may still be required to export data. > >> > >> This fixes

Re: [Mesa-dev] [PATCH 4/4] radv/gfx10: do not always execute a barrier before the second shader

On 7/18/19 2:29 AM, Bas Nieuwenhuizen wrote: On Wed, Jul 17, 2019 at 3:44 PM Samuel Pitoiset wrote: With NGG, empty waves may still be required to export data. This fixes dEQP-VK.ycbcr.format.*_unorm.geometry_*. Signed-off-by: Samuel Pitoiset --- src/amd/vulkan/radv_nir_to_llvm.c | 31

Re: [Mesa-dev] [PATCH 4/4] radv/gfx10: do not always execute a barrier before the second shader

On Wed, Jul 17, 2019 at 3:44 PM Samuel Pitoiset wrote: > > With NGG, empty waves may still be required to export data. > > This fixes dEQP-VK.ycbcr.format.*_unorm.geometry_*. > > Signed-off-by: Samuel Pitoiset > --- > src/amd/vulkan/radv_nir_to_llvm.c | 31 ++- > 1

[Mesa-dev] [PATCH 4/4] radv/gfx10: do not always execute a barrier before the second shader

With NGG, empty waves may still be required to export data. This fixes dEQP-VK.ycbcr.format.*_unorm.geometry_*. Signed-off-by: Samuel Pitoiset --- src/amd/vulkan/radv_nir_to_llvm.c | 31 ++- 1 file changed, 30 insertions(+), 1 deletion(-) diff --git