[Mesa-dev] [PATCH 00/13] GL_ARB_buffer_storage

[Marek Olšák]

I forgot to mention an extension spec bug. The spec mentions
glMemoryBarrier, but doesn't define it anywhere, nor does the spec
define dependencies on other extensions or GL versions.
glMemoryBarrier is required for non-coherent buffer mappings to be
usable. Without it, you have to always use coherent mappings.

glMemoryBarrier is added by GL_ARB_shader_image_load_store and GL 4.2.

I think glMemoryBarrier is always exposed by Mesa no matter what
extensions are supported, but it's an out-of-spec behavior.

Marek

On Thu, Jan 30, 2014 at 2:20 AM, Marek Olšák <maraeo at gmail.com> wrote:
> This series implements GL_ARB_buffer_storage, which most importantly allows rendering with mapped buffers. There is a new test on the piglit mailing list, which should test all aspects of persistent buffer mappings.
>
> I used both the extension specification and the OpenGL 4.4 specification, because the latter adds some GL errors which are not mentioned in the former. This may cause compatibility issues with apps that only target the extension, but all the new GL errors from 4.4 seemed reasonable to me.
>
> u_upload_mgr, the Gallium module for uploading dynamic data to buffers, is updated not to unmap buffers if this extension is supported.
>
> Please review.
>
> Marek