summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2011-08-28getteximage-formats: Test glGetTexImage() for internalformat vs format/type.HEADmasterEric Anholt3-0/+956
2011-08-28ARB_shader_objects/getuniform: New test for glGetUniform* on various types.Eric Anholt5-0/+329
[v2] Test rounding of float to integer, and pretty up the test name in the results.
2011-08-28piglit: Queue up all concurrent tests before starting serial test running.Eric Anholt1-3/+16
Previously, there would be bursts of concurrent tests as we ran into a series of them while walking the list of tests. If we get to the point of the serial tests not being the limiting factor, it might have impacted our total time. Acked-by: Ian Romanick <ian.d.romanick@intel.com>
2011-08-28texwrap: Convert to running concurrently into FBOs.Eric Anholt2-11/+16
Reduces runtime from 26s to 6.7s on my system. Reviewed-by: Marek Olšák <maraeo@gmail.com> Acked-by: Ian Romanick <ian.d.romanick@intel.com>
2011-08-28piglit: Run concurrent tests from as many threads as there are processors.Eric Anholt1-1/+2
Reduces runtime of piglit-run.py -t glslparser from 8.0 seconds to 5.4 seconds on my system. Acked-by: Ian Romanick <ian.d.romanick@intel.com>
2011-08-28piglit: Run the shader_runner fbo tests concurrently.Eric Anholt1-0/+1
Acked-by: Ian Romanick <ian.d.romanick@intel.com>
2011-08-28piglit: Run shader_runner tests into FBOs.Eric Anholt1-1/+2
Acked-by: Ian Romanick <ian.d.romanick@intel.com>
2011-08-28shader_runner: Only swapbuffers if appropriate (!auto, !fbo).Eric Anholt1-1/+1
Acked-by: Ian Romanick <ian.d.romanick@intel.com>
2011-08-28framework: Add an option to run a test into an FBO.Eric Anholt4-29/+215
This is not safe for all tests, but it means we can make some tests run into FBOs and reduce disruption on developer systems. Acked-by: Ian Romanick <ian.d.romanick@intel.com>
2011-08-28Add some tests of source modifiers on VS attributes.Eric Anholt2-0/+52
I managed to drop them in the i965 VS backend.
2011-08-26fs-textureFetchOffset-2D: adds a test for glsl-1.30 texelFetchOffset functionDave Airlie2-0/+137
This applies a small offset to the texel lookups. It passes on softpipe and r600g, but no guarantee its actually correct. Signed-off-by: Dave Airlie <airlied@redhat.com>
2011-08-26fs-texelFetch-2D: add a test for the GLSL 1.30 texelFetch function (v2)Dave Airlie2-0/+131
This is just an initial simple test that just does enough to test TXF development. v2: add some lod testing, not sure what is defined at 1x1 and 2x2 miplevels. Signed-off-by: Dave Airlie <airlied@redhat.com>
2011-08-26glsl-1.30: add texelFetchOffset alternate test.Dave Airlie1-0/+17
this test is a legal version that should pass. Signed-off-by: Dave Airlie <airlied@redhat.com>
2011-08-26texelFetchOffset: fix to show it should fail.Dave Airlie1-1/+1
2011-08-25fs-textureSize-2D: Remove inline keyword.Vinson Lee1-1/+1
MSVC does not support the inline keyword for C.
2011-08-25glsl-1.30: add compiler tests for texelFetch and texelFetchOffset.Dave Airlie2-0/+33
The second one hits an assert in the glsl compiler.. Signed-off-by: Dave Airlie <airlied@redhat.com>
2011-08-25cmake: Don't define min/max macros on Windows.José Fonseca1-0/+3
2011-08-25glsl-1.30: Add compile tests for switch statementsDan McCabe25-0/+554
Included are tests that test both positvely and negatively that the compiler processed valid switch statements and detected syntax errors. Signed-off-by: Dan McCabe <zen3d.linux@gmail.com> Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
2011-08-24glsl-1.20: Ensure that uniform array tests declare the array as a uniformIan Romanick49-97/+97
Reviewed-by: Eric Anholt <eric@anholt.net>
2011-08-24gl-2.0: Add getattriblocation-conventional testIan Romanick6-0/+80
This test verifies that calling glGetAttribLocation on a "conventional" attribute will return -1.
2011-08-24Add an ARB_transform_feedback2 test.Marek Olšák5-0/+196
2011-08-24Add EXT_transform_feedback tests.Marek Olšák7-0/+677
2011-08-23Add new FS execution test for textureSize with 2D textures.Kenneth Graunke5-0/+130
More combinations are obvious: 1D, 3D, Cube, 1DShadow, 2DShadow, CubeShadow, 1DArray, 2DArray, 1DArrayShadow, 2DArrayShadow sampler types, as well as NPOT textures, compressed textures...and calling textureSize in the vertex shader. Reviewed-by: Eric Anholt <eric@anholt.net> Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
2011-08-23Add a piglit_require_GLSL_version(int version) helper function.Kenneth Graunke2-0/+25
Many tests want to check for a specific GLSL version. This helper function makes that really easy: piglit_require_GLSL_version(130); Reviewed-by: Eric Anholt <eric@anholt.net> Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
2011-08-21fbo-depthstencil: also test the default framebufferMarek Olšák2-49/+64
Not really a FBO test, but it may help uncover some bugs.
2011-08-21draw-vertices-2101010: add some more ABI tests also BGRADave Airlie1-1/+41
2011-08-21arb_vertex_type_2_10_10_10_rev: add vertex/color drawing test.Dave Airlie5-0/+213
This is a clone of the general draw-vertices test but adapted to test the ARB_vertex_type_2_10_10_10_rev VBO api.
2011-08-19glsl-1.10 / glsl-1.20: Add non-constant index write testsIan Romanick217-0/+23163
All of these tests follow a similar form. An array of matrices is set to some values that have one incorrect element. A non-constant index write is used to fix that incorrect element. The result is verified. The tests vary on: - Storage qualifier of the array/matrix (uniform, temporary, varying). - Array / not an array. - Matrix size (mat2, mat3, mat4). - Whether or not the array index is a non-constant. - Whether or not the matrix column is a non-constant. - Whether or not the matrix row is a non-constant. Since the base type is always a matrix, attributes and fragment shader outputs are not tested.
2011-08-19glsl-1.10 / glsl-1.20: Add non-constant index read testsIan Romanick433-0/+34772
All of these tests follow a similar form. A simple shader that reads a particular array element, matrix column, and vector element (matrix row) and compares it to some expected value. The tests vary on: - Storage qualifier of the array/matrix (uniform, temporary, varying). - Array / not an array. - Matrix size (mat2, mat3, mat4). - Whether or not the array index is a non-constant. - Whether or not the matrix column is a non-constant. - Whether or not the matrix row is a non-constant. Since the base type is always a matrix, attributes and fragment shader outputs are not tested.
2011-08-19Set rlimit on glsl-*-explosion.shader_test, remove from blacklistIan Romanick5-4/+4
Setting the rlimit should prevent the tests from completely exhausting system memory and swap. Since the tests are more system friendly, they are removed from the blacklist. Acked-by: José Fonseca <jfonseca@vmware.com>
2011-08-19shader_runner: Add rlimit option for shader testsIan Romanick1-0/+13
Acked-by: José Fonseca <jfonseca@vmware.com>
2011-08-19Remove redundant testIan Romanick1-22/+0
This test is made redundant by the spec/glsl-1.20/recursion tests. As is, this test may not have been valid. It expected the error to be generated at compile time, but many implementations generate this error at link time. Acked-by: José Fonseca <jfonseca@vmware.com>
2011-08-19glsl-1.20: Add serveral tests for recursion in shadersIan Romanick6-0/+358
These aren't done as shader_runner tests because there is no way to expect linking or compilation to fail in shader_runner. All of these tests pass on NVIDIA's closed-source driver except 'unreachable' and 'unreachable-constant-folding'. All of these tests fail on AMD's closed-source driver, and 'simple', 'unreachable', and 'unreachable-constant-folding' crash inside the driver. It looks like the compiler tries to recursively inline the functions until the stack overflows. Mesa currently produces pretty much the same results as AMD, but Mesa can occasionally OOM instead of running out of stack. I have not tested Apple's driver or Intel's Windows driver. Reviewed-by: Chad Versace <chad@chad-versace.us> Acked-by: José Fonseca <jfonseca@vmware.com>
2011-08-19Add -rlimit command line option to set the rlimitIan Romanick1-2/+30
Acked-by: José Fonseca <jfonseca@vmware.com>
2011-08-19Add piglit_set_rlimit utility functionIan Romanick4-0/+46
This function sets the maximum amount of memory that a process can have in its address space. This is useful for tests that use "infinite" memory on failing implementations. Setting this low can prevent the test from exhausting system memory and adversely affecting other tests. Acked-by: José Fonseca <jfonseca@vmware.com>
2011-08-18generated tests: Add tests for builtin functions introduced in GLSL 1.30Paul Berry1-0/+32
GLSL 1.30 added support for the following new built-in functions: sinh, cosh, tanh, asinh, acosh, atanh, round, roundEven, trunc, modf, isnan, and isinf. This patch adds tests for all of the new built-in functions except modf, isnan, and isinf. modf will need to be tested separately because it has an out parameter; isnan and isinf will need to be tested separately because producing infinite and NaN values will require extra work in the shader. Reviewed-by: Chad Versace <chad@chad-versace.us>
2011-08-18generated tests: Test operators that were introduced in GLSL 1.30Paul Berry1-0/+114
GLSL 1.30 adds support for the following operators: %, ~, <<, >>, &, ^, and |. This patch adds autogenerated tests for testing the functionality of all these operators. Reviewed-by: Chad Versace <chad@chad-versace.us>
2011-08-18generated tests: Add uint and int tests for GLSL 1.30.Paul Berry3-34/+72
GLSL 1.30 allows int and ivecN types to be passed to the functions abs, sign, min, max, and clamp. In addition, it adds new unsigned integer types uint and uvecN, which may be passed to min, max, clamp, lessThan, lessThanEqual, greaterThan, greaterThanEqual, equal, notEqual, and built-in operators. This patch adds auto-generated tests for all of these new integral built-in functions and operations. Reviewed-by: Chad Versace <chad@chad-versace.us>
2011-08-18Add uint and uvec uniform support to shader_runner.Paul Berry1-0/+30
With this patch, shader_runner tests can now supply uniform values using types "uint" and "uvecN". Reviewed-by: Chad Versace <chad@chad-versace.us>
2011-08-18Make uniform uint and int functions callable from piglit tests.Paul Berry2-0/+36
This patch adds glUniform{1,2,3,4}ui and glUniform{1,2,3,4}uiv to the set of GL functions available through aliases beginning with "piglit_", so that they can be called from piglit tests in the same manner as other OpenGL functions. Also added the missing versions of glUniform{1,2,3,4}i and glUniform{1,2,3,4}iv. Reviewed-by: Chad Versace <chad@chad-versace.us>
2011-08-18generated tests: Add builtin tests using if.Paul Berry1-17/+110
For builtin functions and operators returning bool, added generated tests that use the return values in if statements like this: if (a < b) gl_FragColor = vec4(1.0, 1.0, 0.0, 1.0); else gl_FragColor = vec4(0.0, 0.0, 1.0, 1.0); in addition to the existing tests that convert the return values to floats, like this: bool result = a < b; gl_FragColor = vec4(result, 0.0, 0.0, 0.0); Since implementations may produce substantially different GPU code for these two cases. Reviewed-by: Chad Versace <chad@chad-versace.us>
2011-08-18generated tests: Added tests for the 'notEqual' builtin.Paul Berry1-0/+1
This function has been available since as early GLSL 1.10, it was simply forgotten from the initial implementation of generated tests. Reviewed-by: Chad Versace <chad@chad-versace.us>
2011-08-18generated tests: Expand the range of ints and ivecs used in testing.Paul Berry1-2/+6
This patch adds negative and zero values to the set of ints used to test lessThan, lessThanEqual, greaterThan, greaterThanEqual, and equal. It also adds ivecs whose elements are all positive to the tests for operators--these will come in handy when we add tests for %, which is not defined for negative inputs. Reviewed-by: Chad Versace <chad@chad-versace.us>
2011-08-18generated tests: Make test generation happen in a deterministic order.Paul Berry2-2/+2
This patch makes gen_builtin_uniform_tests.py and gen_constant_array_size_tests.py build tests in a deterministic order, so that when diffing their outputs from one revision to the next, it is easier to see what changed. There is no change in the actual tests generated, just in the *.list files that are created as a side effect. Reviewed-by: Chad Versace <chad@chad-versace.us>
2011-08-16select,fp-unpack-01: Define round() & roundf() for MSVC in a single place.José Fonseca2-7/+16
Should fix MSVC build.
2011-08-15Add GL_SELECT render mode testsPierre-Eric Pelloux-Prayer3-0/+266
2011-08-15Add operator tests to auto-generated built-in function tests.Paul Berry3-69/+266
This patch adds tests for the following built-in GLSL operators: - op-add, op-sub, op-mult, op-div: binary arithemetic operators on floats, vecs, mats, ints, and ivecs. - op-uplus, op-neg: unary arithmetic operators on floats, vecs, mats, ints, and ivecs. - op-gt, op-lt, op-ge, op-le: comparison operators on ints and floats. - op-eq, op-ne: equality and inequality comparison on any GLSL 1.20 type. - op-and, op-or, op-xor: logical operations on bools. - op-not: unary logical not on bools. - op-selection: trinary selection operator (x?y:z), where the first argument is a bool and the second and third arguments are any GLSL 1.20 type. Note that implicit type conversions are not tested. So, for instance, int * ivec is tested, but float * ivec is not. This was in an effort to avoid generating an outrageous number of tests. Note also that the "shortcut" behavior of logical and/or and trinary selection is not tested. These tests leverage the same test generation framework used to test built-in functions, so the tests exercise vertex shaders, fragment shaders, and constant folding. All in all 1332 tests are added, in the subtrees spec/glsl-1.{10,20}/{compiler,execution}/built-in-functions. Reviewed-by: Eric Anholt <eric@anholt.net>
2011-08-14quick-driver.tests: add back blendFunc and depthStencilMarek Olšák1-3/+0
2011-08-12Fix Python 2.6 incompatibility in str.decode() function.Paul Berry1-2/+2
In Python 2.6, the str.decode() function can't take keyword arguments, so x.decode(y, errors=z) must be changed to x.decode(y, z). There is no difference in functionality. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=40051
2011-08-11README: Add build instructions for Cygwin.Vinson Lee1-0/+23
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-13 23:53:42 +0000