[Piglit] [PATCH] arb_shader_clock: fix use of atomic counters
Dave Airlie
airlied at gmail.com
Thu Nov 30 00:22:47 UTC 2017
From: Dave Airlie <airlied at redhat.com>
This test was trying to use two atomic counters at different
buffer bindings, but the shader runner just allocates one bo,
so just use the same binding, they will end up sequential.
---
tests/spec/arb_shader_clock/execution/clock.shader_test | 2 +-
tests/spec/arb_shader_clock/execution/clock2x32.shader_test | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/spec/arb_shader_clock/execution/clock.shader_test b/tests/spec/arb_shader_clock/execution/clock.shader_test
index 07530e6..c7c9116 100644
--- a/tests/spec/arb_shader_clock/execution/clock.shader_test
+++ b/tests/spec/arb_shader_clock/execution/clock.shader_test
@@ -12,7 +12,7 @@ GL_ARB_shader_clock
layout(local_size_x = 1) in;
layout(binding = 0) uniform atomic_uint good;
-layout(binding = 1) uniform atomic_uint bad;
+layout(binding = 0) uniform atomic_uint bad;
layout(std430, binding = 0) buffer ssbo_data {
uint64_t ssbo_time[];
diff --git a/tests/spec/arb_shader_clock/execution/clock2x32.shader_test b/tests/spec/arb_shader_clock/execution/clock2x32.shader_test
index 1a2bfef..e20f797 100644
--- a/tests/spec/arb_shader_clock/execution/clock2x32.shader_test
+++ b/tests/spec/arb_shader_clock/execution/clock2x32.shader_test
@@ -10,7 +10,7 @@ GL_ARB_shader_clock
layout(local_size_x = 1) in;
layout(binding = 0) uniform atomic_uint good;
-layout(binding = 1) uniform atomic_uint bad;
+layout(binding = 0) uniform atomic_uint bad;
layout(std430, binding = 0) buffer ssbo_data {
uvec2 ssbo_time[];
--
2.9.5
More information about the Piglit
mailing list