<p dir="ltr">On Tue, Nov 3, 2015 at 8:40 PM, Ilia Mirkin <<a href="mailto:imirkin@alum.mit.edu">imirkin@alum.mit.edu</a>> wrote:<br>
> Ian, any comment on this?<br>
><br>
> On Fri, Sep 25, 2015 at 1:32 PM, Ilia Mirkin <<a href="mailto:imirkin@alum.mit.edu">imirkin@alum.mit.edu</a>> wrote:<br>
>> Hi Ian (and other spec experts),<br>
>><br>
>> The ARB_ssbo spec mentions the following:<br>
>><br>
>> OpenGL 4.0 (either core or compatibility profile) is required.<br>
>><br>
>> ...<br>
>><br>
>> Additionally, the shading language provides the memoryBarrier() function<br>
>> to control the relative order of memory accesses within individual shader<br>
>> invocations and provides various memory qualifiers controlling how the<br>
>> memory corresponding to individual variables is accessed.<br>
>><br>
>> However the memoryBarrier() function only becomes available in GLSL<br>
>> 4.20 [along with the glMemoryBarrier() function that the spec also<br>
>> refers to] or with ARB_shader_image_load_store.<br>
>><br>
>> Is the implication that such functionality should be auto-exposed in<br>
>> image-less drivers that support ssbo? Or that this functionality<br>
>> should just not exist unless images are supported?</p>
<p dir="ltr">That looks like a spec bug. If the spec says "the shading language provides the memoryBarrier", it should provide it.</p>
<p dir="ltr">Marek</p>