[Piglit] [PATCH] ext_framebuffer_blit: Verify framebuffer bindings after calling glGenerateMipmap

From: Ian Romanick Mesa's meta path for glGenerateMipmap had a problem that it assumed the two bindings were the same. As a result, one of them was incorrect after returning from _mesa_meta_GenerateMipmap. NOTE: This currently fails on all Mesa drivers that use

Re: [Piglit] [PATCH 1/6] shader_runner: Check feature support before querying GL_MAX_*.

On Wed, Nov 11, 2015 at 4:47 PM, Kenneth Graunke wrote: > On Tuesday, November 10, 2015 10:46:18 PM Matt Turner wrote: >> Otherwise, these will generate an error (to be noticed sometime later >> when glGetError() is called), often resulting in a test failure. >> --- >>

Re: [Piglit] [PATCH] ext_framebuffer_blit: Verify framebuffer bindings after calling glGenerateMipmap

On Fri, Nov 13, 2015 at 2:54 PM, Ian Romanick wrote: > From: Ian Romanick > > Mesa's meta path for glGenerateMipmap had a problem that it assumed the > two bindings were the same. As a result, one of them was incorrect > after returning from

Re: [Piglit] [PATCH v1] Porting the OpenGL shading language from Glean to Piglit.

On Tue, Oct 20, 2015 at 12:16 AM, Juliet Fru wrote: > Hi Brian, > > I have been working on the "gl_Position not written check" > (tests/spec/glsl-1.10/linker/) test from glean to shader_test files. Here is > what I have so far. I'm sure there may be some errors since this

Re: [Piglit] [PATCH] ext_framebuffer_blit: Verify framebuffer bindings after calling glGenerateMipmap

On 11/13/2015 12:04 PM, Ilia Mirkin wrote: > On Fri, Nov 13, 2015 at 2:54 PM, Ian Romanick wrote: >> From: Ian Romanick >> >> Mesa's meta path for glGenerateMipmap had a problem that it assumed the >> two bindings were the same. As a result, one