Am 04.04.2013 01:55, schrieb Brian Paul:
On 04/03/2013 05:14 PM, srol...@vmware.com wrote:
From: Roland Scheideggersrol...@vmware.com
Similar to arb_shader_texture_lod-texgrad, but using cube maps instead.
Given the somewhat undefined behavior of explicit gradients with cube
maps, the main
Stuart Abercrombie sabercrom...@chromium.org writes:
It will be added based on the GLSL requirement instead.
Same number of passes on Sandy Bridge running all.tests without glean.
I don't like this anti-#version crusade. I'd like to see only patches
to remove them if it actually makes the
TEST status:
IsProgramPipeline:
* neither AMD/NVIDIA follow the spec...
* Crash on AMD: because of -1 of glGenProgramPipelines( -1, id)
* Crash on Nvidia: glGetProgramPipelineiv(4, GL_VERTEX_SHADER, value).
GetProgramPipelineiv:
* working on nvidia
* FGLRX only accept as
Equivalent to piglit_link_check_status/quiet but with program object pipeline
---
tests/util/piglit-shader.c | 50
tests/util/piglit-shader.h |2 ++
2 files changed, 52 insertions(+)
diff --git a/tests/util/piglit-shader.c
On Thu, Apr 4, 2013 at 11:11 AM, Eric Anholt e...@anholt.net wrote:
Stuart Abercrombie sabercrom...@chromium.org writes:
It will be added based on the GLSL requirement instead.
Same number of passes on Sandy Bridge running all.tests without glean.
I don't like this anti-#version crusade.
I've basically been following the sequence Paul Berry suggested here:
http://lists.freedesktop.org/archives/piglit/2012-August/003162.html.
It seems to be a reasonable way of getting to a point where some subset of
.shader_test scripts can be run with both GL and GLES.
As far as I know, removing
Am 04.04.2013 17:48, schrieb Brian Paul:
On 04/04/2013 09:33 AM, Roland Scheidegger wrote:
Am 04.04.2013 01:55, schrieb Brian Paul:
On 04/03/2013 05:14 PM, srol...@vmware.com wrote:
From: Roland Scheideggersrol...@vmware.com
Similar to arb_shader_texture_lod-texgrad, but using cube maps
