[Piglit] [PATCH] shader_runner: Only call glMemoryBarrier when supported

[Jordan Justen]

On Sun, Jun 22, 2014 at 10:49 PM, Kenneth Graunke <kenneth at whitecape.org> wrote:
> On Saturday, June 21, 2014 08:34:05 PM Chris Forbes wrote:
>> Ian,
>>
>> That's true, but... we will probably have compute finished long before
> images.
>>
>> Is there an acceptable thing to do here in the interim?
>>
>> -- Chris
>
> How?  As I understand it, compute shaders can really only output anything via
> ARB_shader_image_load_store or ARB_shader_storage_buffer_object.  And if they
> can't output anything, what's the point of having them?
>
> Perhaps I'm mistaken, and you can do useful things with them...I guess you
> could maybe just use atomic buffers, but...

tests/spec/arb_compute_shader/execution/atomic-counter.shader_test

Another thought might be that the memory barrier call could be a
separate shader runner command.

-Jordan