radv: drop wrong initialization of COMPUTE_RESOURCE_LIMITS
authorSamuel Pitoiset <samuel.pitoiset@gmail.com>
Tue, 14 Aug 2018 16:11:48 +0000 (18:11 +0200)
committerSamuel Pitoiset <samuel.pitoiset@gmail.com>
Wed, 15 Aug 2018 14:20:38 +0000 (16:20 +0200)
commit17e79865cf3c8be2a710427a0a5c9b3bafeddf78
tree4dec56704c1cf20db5c5d99c70a6c7aa46895384
parent53b4701cb07da8c70eca240ad5e159e1b9ce8bf4
radv: drop wrong initialization of COMPUTE_RESOURCE_LIMITS

The last parameter of radeon_set_sh_reg_seq() is the number of
dwords to emit. We were lucky because WAVES_PER_SH(0x3) is 3 but
it was initialized to 0.

COMPUTE_RESOURCE_LIMITS is correctly set when generating
compute pipelines, so we don't need to initialize it.

Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
Reviewed-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
src/amd/vulkan/si_cmd_buffer.c