| Age | Commit message (Collapse) | Author |
|---|
|
Conflicts:
generated_tests/CMakeLists.txt
|
|
outerProduct is available with glsl es 3.00 but not
with glsl es 1.00.
http://www.khronos.org/opengles/sdk/docs/manglsl/xhtml/outerProduct.xml
|
|
|
|
|
|
|
|
|
|
|
|
|
|
As these tests are now autogenerated in generated_tests by
variable-index-read.sh and variable-index-write, remove them.
|
|
|
|
From tests/spec/glsl-1.10 extend variable-index-write.sh so that
it can also correctly generates variable index write tests that
support glsl-es-1.00.
1.00 added as a valid parameter to generated tests for glsl-es-1.00.
For 1.00 tests in the vertex shader an orthographic projection is
applied since ortho during the test portion isn't supported on
OpenGL ES.
For 1.00 tests the fragent shader specifies default precision.
For 1.00 tests emit in the [require] section the correct
GLSL ES and GL ES settings.
|
|
From tests/spec/glsl-1.10 extend variable-index-read.sh so that
it can also correctly generates variable index read tests that
support glsl-es-1.00.
1.00 added as a valid parameter to generated tests for glsl-es-1.00.
For 1.00 tests the vertex shader an orthographic projection is
applied since ortho during the test portion isn't supported on
OpenGL ES.
For 1.00 tests the fragent shader specifies default precision.
For 1.00 tests emit in the [require] section the correct
GLSL ES and GL ES settings.
|
|
v3: Made more readable, report observed sample positions of failure.
|
|
From the description of glMapBuffer:
"A mapped data store must be unmapped with glUnmapBuffer before its
buffer object is used.
Otherwise an error will be generated by any GL command that
attempts to dereference the buffer object's data store."
|
|
Since we never bail on the first failure in this test, we can return
from the GetInternalformativ without buffer_size_in_elements ever
being touched, due to misc GL error (mesa_base_fbo_format fails),
this then causes us to loop a lot later and print error messages
than make piglit eat all the pies^WRAM.
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
Changes:
- SINGLE is removed, because its value was 0
- ALPHA is removed, because it becomes redundant with this change
- RGB asks for an RGB visual
- RGBA asks for an RGBA visual
- if RGB and RGBA are unset, it asks for a visual without RGB(A)
Reviewed-by: Brian Paul <brianp@vmware.com>
Reviewed-by: Chris Forbes <chrisf@ijw.co.nz>
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
v2: fix glut
|
|
By the looks of it "default" is not required to appear as last statement
in a switch expression, and c rules should be followed (which is probably
a mess to implement thanks to fallthrough).
Seems to fail with mesa glsl compiler (at least with tgsi translation).
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
|
|
v2: Fix "written" subtest (which was testing the wrong query).
Reviewed-by: Eric Anholt <eric@anholt.net>
|
|
GLSL ES 1.00 spec 4.5.3 page 36:
"The fragment language has no default precision qualifier for
floating point types."
Adding default precision for float in the fragment shader
so this sanity testcase doesn't error out.
mediump is choosen since according to 4.5.2 page 34:
"The fragment language requires any uses of lowp and mediump to
compile without error. Support for highp is optional."
Signed-off-by: Tom Gall <tom.gall@linaro.org>
Reviewed-by: Stuart Abercrombie <sabercrombie@chromium.org>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
|
|
Commit 0fac0a6 (Modify tests for error checking on "flat" keyword to
match updated specs) adopted the GLSL 1.50 rules for "flat" varyings
for all desktop GL tests (the rationale was that this change likely
reflects a bug fix rather than a deliberate behavioural difference).
The GLSL 1.50 rules allow a vertex shader output to be a non-flat
integer provided that it isn't consumed by the fragment shader. In
particular, this means that a non-flat integer may be used with
transform feedback.
This test verifies that transform feedback works correctly for all
integral types, even if they are not declared as "flat".
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Reviewed-by: Jose Fonseca <jfonseca@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 purpose of the test is really to test that those work at
all, as there doesn't seem to be any other test covering this.
That said, drivers which simply drop explicit derivatives on the floor
(like softpipe) pass this perfectly as it simply compares implicit vs.
explicit behavior (which, given the fuzzy specification, might not be
really required to be the same here, though given the chosen values, that
is the major axis derivatives being zero, it might seem like a reasonable
assumption).
I guess something which would also test that the implementation is really
using explicit derivatives instead of implicit ones would also be desirable,
but I'll leave that for now, I couldn't really come up with something.
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
__func__ is not available on MSVC.
Signed-off-by: Vinson Lee <vlee@freedesktop.org>
|
|
One of the challenging aspects of testing this extension is that it
defines an implementation-specific set of groups and counters. Many of
the tests here arbitrarily operate on the counters in the first group,
while a few sanity check all counters in all groups.
All tests pass on AMD's Catalyst 12.06 driver on a Radeon 3650, except
for: test_number_of_groups_partial_array, test_delete_monitor_invalid,
and test_get_counter_data_byte_size. I believe the first two are
legitimate bugs in AMD's implementation, and the latter is a
disagreement about the associativity of text within a paragraph. Still,
these are minor details and I believe the tests are valid.
v2: Actually set the test name for the second test.
Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
v2: Use textureQueryLOD instead of textureQueryLOD.
|
|
v2: Use textureQueryLOD instead of textureQueryLOD.
|
|
v2: Use textureQueryLOD instead of textureQueryLOD.
|
|
v2: Use textureQueryLOD instead of textureQueryLOD.
|
|
This covers the sample count limits for both renderbuffers and
multisample textures, when ARB_texture_multisample is supported.
Skips if ARB_internalformat_query is supported, since that extension
allows the overall sample count limits to be exceeded on a
per-internalformat basis.
V2: - Emit a useful message when skipping.
V3: - Style nits
Signed-off-by: Chris Forbes <chrisf@ijw.co.nz>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
If ARB_texture_multisample or ARB_internalformat_query are supported,
the limits and/or errors generated are different, so skip this test.
V2: - Emit a useful message when skipping.
V3: - Indentation
Signed-off-by: Chris Forbes <chrisf@ijw.co.nz>
Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
|
|
v2: cosmetic changes as suggested by Eric
|
|
It will be added based on the GLSL requirement instead.
Also make it clearer that these shader_test files are automatically generated.
Same number of passes on Sandy Bridge running all.tests without glean.
v2: Add missing comment #
Signed-off-by: Stuart Abercrombie <sabercrombie@chromium.org>
Reviewed-by: Eric Anholt <eric@anholt.net>
Reviewed-by: Tom Gall <tom.gall@linaro.org>
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
|
|
This test provides a complex test of using interface blocks.
Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Stuart Abercrombie <sabercrombie@chromium.org>
|
|
A few tests to make sure that interface blocks are defined
the same during intrastage and interstage linking.
Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Stuart Abercrombie <sabercrombie@chromium.org>
|
|
Catches an assertion failure/rendering failure in i965.
|
|
|
|
Adds gl_MaxCombinedTextureImageUnits.shader_test
gl_MaxDrawBuffers.shader_test
gl_MaxFragmentUniformVectors.shader_test
gl_MaxTextureImageUnits.shader_test
gl_MaxVaryingVectors.shader_test
gl_MaxVertexAttribs.shader_test
gl_MaxVertexTextureImageUnits.shader_test
gl_MaxVertexUniformVectors.shader_test
These check the built-in constants of the same name from
section 7.4 of the glsl es 1.0.17 spec.
v2: squash patch, address one by one spec reference.
Signed-off-by: Tom Gall <tom.gall@linaro.org>
Reviewed-by: Eric Anholt <eric@anholt.net>
|
|
Signed-off-by: Brian Paul <brianp@vmware.com>
|
|
waffles-decompressed-etc2-r11-64x32-miptree.ktx contains per pixel RGBA data
generated by ericsson's etcpack tool. While generating decompressed image
for COMPRESSED_R11_EAC format, RED color data for each pixel is copied to
GREEN and BLUE channels as well. Using this image for texturing in OpenGL ES
3.0 (internalFormat=GL_R8) causes GL_INVALID_OPERATION. This is because
glTexImage2D() in GL ES 3.0 doesn't allow internalFormat = GL_R8 with
format= GL_RGBA. To workaround this issue use internalFormat = GL_RGBA and
mask all color channels except Red.
Other option is to edit the waffles-decompressed-etc2-r11-64x32-miptree.ktx
file and set all GREEN, BLUE components to zero. Considering the hassle involved
in editing image file, I won't prefer that.
This fixes the piglit failure on gles3 with COMPRESSED_R11_EAC format.
Signed-off-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
Mimic others CMakeLists.gl.txt
|
|
V2: Enable the test to choose core/compat GL context at run time.
Add GL version of test to all.tests.
Use VAO to enable the test run on core context.
Reviewed-by: Matt Turner <mattst88@gmail.com>
|
|
Signed-off-by: Adam Jackson <ajax@redhat.com>
|
|
This is pretty rough and doesn't really test all that much (just
textureOffsetLod, but there's other texturing functions with offsets),
doesn't test different wrap modes, NPOT sizes etc., but there's no
other test using "ordinary" texture opcodes and texel offsets, so
it's a start (and in fact it exposed a bug in the mesa state tracker).
Tested with llvmpipe (pass) and softpipe (fail) which is as expected -
hopefully the math is ok...
Inspired from fs-texelFetchOffset.
v2: some minor comment and code fixes
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
In order to fix the build on MSVC, which does not support them.
|
|
Tests that glFramebufferTextureLayer produces the correct error for
layer < 0 when used with GL_TEXTURE_2D_MULTISAMPLE_ARRAY. This was
overlooked in the initial mesa implementation of
ARB_texture_multisample, and crashed deep in the driver instead.
V3: - Don't set the window size, we don't care.
V4: - Add missing copyright notice.
Signed-off-by: Chris Forbes <chrisf@ijw.co.nz>
|
|
Adds tests for sample mask:
- Initial state
- Fetching of each sample mask word
- Execution test via rendering with various masks to a multisample FBO,
then downsampling via glBlitFramebuffer and checking the result.
V2: - Don't specify window size when we don't care.
V4: - Add missing copyright notice.
Signed-off-by: Chris Forbes <chrisf@ijw.co.nz>
|
