If the piglit_display() function was called more than once, we'd
try use deleted textures and generate a bunch of GL errors.
---
tests/spec/arb_clear_texture/simple.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/tests/spec/arb_clear_texture/simple.c
b/tests/spec/arb_clear_texture/simple.c
Instead of a local helper function.
---
tests/spec/arb_sampler_objects/sampler-objects.c | 20
1 file changed, 4 insertions(+), 16 deletions(-)
diff --git a/tests/spec/arb_sampler_objects/sampler-objects.c
b/tests/spec/arb_sampler_objects/sampler-objects.c
index
On 22/07/15 18:25, Brian Paul wrote:
errors.c - test error detection
get.c - test glGetTextureSubImage
getcompressed.c - test glGetCompressedTextureSubImage
cubemap.c - extra tests for getting cubemap images
v2:
move guts of the tests from piglit_display() to piglit_init(),
test cube map
On 24 July 2015 at 02:00, Neil Roberts n...@linux.intel.com wrote:
Adds a test which is similar to interpolateAtSample-different except
that it draws a triangle which covers more than one fragment and makes
sure to use a different sample ID for each fragment so that it won't
be dynamically
On Fri, Jul 17, 2015 at 03:57:59PM +0100, Jose Fonseca wrote:
Python3 will definitely bring challenges to us.
It's no problem for our personal development systems, but there are
several systems which still only have python 2.x -- (systems we want to
run or build piglit.)
I wonder it
Adds a test which is similar to interpolateAtSample-different except
that it draws a triangle which covers more than one fragment and makes
sure to use a different sample ID for each fragment so that it won't
be dynamically uniform. The GLSL spec doesn't mention that the sample
ID has to be
On Wed, 2015-07-22 at 21:39 -0700, Kenneth Graunke wrote:
Mesa's compiler happened to handle .xzy.z correctly, while .xy.x and
other combinations were broken. Try that and a triply-nested one.
Cc: i...@freedesktop.org
Signed-off-by: Kenneth Graunke kenn...@whitecape.org
---
