Problem with releasing already released objects originates from ICD
Loader, which requires that object is alive when calling OpenCL host
functions. Khronos ICD Loader specs
(http://www.khronos.org/registry/cl/extensions/khr/cl_khr_icd.txt) says:
At every OpenCL function call, the ICD
On 08/21/2013 09:44 PM, Ian Romanick wrote:
From: Ian Romanick ian.d.roman...@intel.com
Many of these tests fail on older GPU such as Intel i915 due to the
precision requirement. This is because many GPUs in this class only use
24-bit floats. Many also implement many instructions cheaply
add new test to existing arb_seamless_cube_map group: sample three adjoining
faces and use average. if three faces are the same color, that color must
be used.
add test to makelists and all.tests
V2 : test now uses contemporary pipeline
---
tests/all.tests
On 20 August 2013 10:56, Nicholas Mack nichm...@gmail.com wrote:
---
tests/spec/CMakeLists.txt | 1 +
tests/spec/arb_provoking_vertex/CMakeLists.gl.txt | 14
tests/spec/arb_provoking_vertex/CMakeLists.txt | 1 +
.../provoking-vertex-control.c
On 20 August 2013 10:56, Nicholas Mack nichm...@gmail.com wrote:
Note: The spec refers to QUADS_FOLLOW_PROVOKING_VERTEX but this is a spec
bug.
---
tests/spec/arb_provoking_vertex/CMakeLists.gl.txt | 1 +
.../quads-follow-provoking-vertex.c| 64
++
2
On 20 August 2013 10:56, Nicholas Mack nichm...@gmail.com wrote:
---
tests/spec/arb_provoking_vertex/CMakeLists.gl.txt | 1 +
.../arb_provoking_vertex/xfb-before-flatshading.c | 203
+
2 files changed, 204 insertions(+)
create mode 100644
On 20 August 2013 10:56, Nicholas Mack nichm...@gmail.com wrote:
---
tests/spec/arb_provoking_vertex/CMakeLists.gl.txt | 1 +
.../provoking-vertex-initial.c | 64
++
2 files changed, 65 insertions(+)
create mode 100644
On 20 August 2013 16:04, Anuj Phogat anuj.pho...@gmail.com wrote:
Signed-off-by: Anuj Phogat anuj.pho...@gmail.com
---
tests/spec/ext_framebuffer_multisample/common.cpp | 18 ++
1 file changed, 2 insertions(+), 16 deletions(-)
Series is:
Reviewed-by: Paul Berry
---
.../built-in-functions/fs-frexp.shader_test| 64 ++
1 file changed, 64 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-frexp.shader_test
diff --git
---
.../built-in-functions/vs-frexp.shader_test| 68 ++
1 file changed, 68 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/vs-frexp.shader_test
diff --git
---
.../built-in-functions/fs-ldexp.shader_test| 88 ++
1 file changed, 88 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-ldexp.shader_test
diff --git
---
.../built-in-functions/vs-ldexp.shader_test| 93 ++
1 file changed, 93 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/vs-ldexp.shader_test
diff --git
---
.../built-in-functions/vs-fma.shader_test | 62 ++
1 file changed, 62 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/vs-fma.shader_test
diff --git
---
.../built-in-functions/fs-fma.shader_test | 58 ++
1 file changed, 58 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/fs-fma.shader_test
diff --git
---
.../built-in-functions/const-fma.shader_test | 38 ++
1 file changed, 38 insertions(+)
create mode 100644
tests/spec/arb_gpu_shader5/execution/built-in-functions/const-fma.shader_test
diff --git
I probably should mention that the first two patches of the four patches is
meant to fix some problems with compatibility fall back... The problem is
caused by the test suite note resetting the variable that stores the list
of supported extensions after the old context is destroyed. There is a
This must've been cut and pasted from a vertex shader by accident.
Signed-off-by: Kenneth Graunke kenn...@whitecape.org
Cc: Nicholas Mack nichm...@gmail.com
---
tests/spec/glsl-1.50/compiler/layout-global-only.frag | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
17 matches
Mail list logo