If I'm reading the grammar correctly, the constant offset must be in
the range [-64, 63]:
addrRegRelOffset ::=
| + addrRegPosOffset
| - addrRegNegOffset
addrRegPosOffset ::= integer from 0 to 63
addrRegNegOffset
On Mon, Jun 10, 2013 at 1:49 PM, Marek Olšák mar...@gmail.com wrote:
If I'm reading the grammar correctly, the constant offset must be in
the range [-64, 63]:
addrRegRelOffset ::=
| + addrRegPosOffset
| - addrRegNegOffset
New test for loading texture data from one thread and context while drawing
with those textures from another thread and shared context. The threads are
synchronized so they do not attempt to use the same texture at the same time.
Signed-off-by: Frank Henigman fjhenig...@google.com
---
Add primitives with adjacency and (for extreme future-proofness) patches to
recognized drawing modes.
---
tests/shaders/shader_runner.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/tests/shaders/shader_runner.c b/tests/shaders/shader_runner.c
index 515fde1..e022b90
This is usefull for core profile OpenGL contexts and geometry shaders.
---
tests/util/piglit-util-gl.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/tests/util/piglit-util-gl.c b/tests/util/piglit-util-gl.c
index 0a56582..04c36bb 100644
---
Test that glProgramParameter() triggers the required errors.
The geometry shader input primitive type is limited to a subset
of OpenGL primitive types.
From the ARB_geometry_shader4 spec (section Errors):
The error INVALID_VALUE is generated by ProgramParameteriARB if pname is
It used to be piglit_width which works, too, as the framebuffer is hardcoded
to 250x250 pixels.
---
tests/shaders/shader_runner.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/shaders/shader_runner.c b/tests/shaders/shader_runner.c
index 7fc74aa..515fde1 100644
---
Test that glProgramParameter() triggers the required errors.
The geometry shader output primitive type is limited to a subset
of OpenGL primitive types.
From the ARB_geometry_shader4 spec (section Errors):
The error INVALID_VALUE is generated by ProgramParameteriARB if pname is
---
.../execution/generate-zero-primitives.shader_test | 55 ++
1 file changed, 55 insertions(+)
create mode 100644
tests/spec/arb_geometry_shader4/execution/generate-zero-primitives.shader_test
diff --git
Test that glProgramParameter() triggers the required errors.
The value of GEOMETRY_VERTICES_OUT is limited by the implementation
dependend constants MAX_GEOMETRY_OUTPUT_VERTICES and
MAX_VERTEX_VARYING_COMPONENTS.
From the ARB_geometry_shader4 spec (section Errors):
The error INVALID_VALUE is
Test that linking fails without vertex shader present.
ARB_geometry_shader4 spec 2.15.2:
Linking will also fail if the program object contains objects to form a
geometry shader (see section 2.16), but no objects to form a vertex shader
---
.../linker/no-vertex-shader.shader_test| 32
Test that linking fails if the geometry shader accesses more components than
are available.
ARB_geometry_shader4 spec 2.16.1:
However, a program object, containing a shader object that access more input
vertices than are available for the input primitive type of the program
object, will not link.
All geometry shader input varyings are arrays.
Array varyings are two-dimensional arrays.
Test indexing of scalar, vector and matrix varyings.
---
.../arb_geometry_shader4/compiler/array-index.geom | 35 ++
1 file changed, 35 insertions(+)
create mode 100644
Test basic indexing operations with 2d arrays.
---
.../arb_geometry_shader4/compiler/2darray01.geom | 63 +++
.../linker/2darray01.shader_test | 70 ++
2 files changed, 133 insertions(+)
create mode 100644
Test that gl_VerticesIn can be used as a valid constant expression.
Also test that it evaluates to 3 for triangles.
---
.../compiler/verticesin-const-expression.geom | 31
.../compiler/verticesin-const.geom | 31
.../linker/verticesin-const.shader_test
Add some tests that basically check that the compiler doesn't confuse the two
array dimensions.
---
.../arb_geometry_shader4/compiler/2darray02.geom | 29
.../arb_geometry_shader4/compiler/2darray03.geom | 29
.../arb_geometry_shader4/compiler/2darray04.geom | 30
From the ARB_geometry_shader4 spec (section ):
Indices used to subscript gl_TexCoord must either be an integral constant
expressions, or this array must be re-declared by the shader with a size.
And from the GLSL 1.1 spec page 99 (page 105 of the PDF):
Multiple modules can declare it
Fabian Bieler fabianbie...@fastmail.fm writes:
Add primitives with adjacency and (for extreme future-proofness) patches to
recognized drawing modes.
---
tests/shaders/shader_runner.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/tests/shaders/shader_runner.c
18 matches
Mail list logo
