| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
this just checks the basic API works.
Conflicts:
tests/spec/CMakeLists.txt
|
|
|
|
this just writes attribs and reads the current value back.
|
|
Check the double value unpacks cleanly in the fragment shader.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
This just tests the preprocessor defines appear in the shaders.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
This is just a simple 64-bit vertex attrib test.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
I noticed the TGSI convertor just does INEG then AND 0x3f800000, which works
for small values, but fails for larger ints.
This seems to fail on nvidia (4.3.0 NVIDIA 325.15) and on ironlake with mesa
9.2.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
otherwise with 32-bit depth tolerance can be < 0 making the test fail for no
reason, as 0 > negative tolerance.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
These tests go through the builtins with goal of testing constant
expression support for the double type.
Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
|
|
glClientWaitSync(fence, GL_SYNC_FLUSH_COMMANDS_BIT, GL_TIMEOUT_IGNORED)
may return GL_TIMEOUT_EXPIRED, even though GL_TIMEOUT_IGNORED is a huge
integer (18446744073709551615 on Intel Sandybridge with Mesa). The third
argument to glClientWaitSync should represent the number of nanoseconds the
implementation waits for the signal from fence before giving up and returning
TIMEOUT_EXPIRED.
This test, adapted from bufferstorage-persistent, demonstrates that
glClientWaitSync(fence, GL_SYNC_FLUSH_COMMANDS_BIT, GL_TIMEOUT_IGNORED)
must be called multiple times before the signal is actually recorded and
either GL_CONDITION_SATISFIED or GL_ALREADY_SIGNALED is returned.
This bug was successfully fixed by Mesa commit 10c82c6 by Kristian Hogsberg.
Reviewed-by: Martin Peres <martin.peres@linux.intel.com>
|
|
This test reproduces the cause of Mesa Bug 89526 in Piglit. While
investigating 89526, it was discovered that Piglit had no tests that created a
cube map texture without glTexStorage2D and then called glGenerateMipmap on
it. For this reason, the offending commit was upstreamed before the failure
was caught.
This test successfully fails when commit 1ee000a is present and passes when
1ee000a is reverted.
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
A common error in all.py is that two different tests are assigned to the
same key value in profile.test_list. This change prevents a key from
being reassigned to a new value on accident, but provides a mechanism to
allow reassignment, using a context manager. This allows tests like the
image_load_store tests in quick.py to be overwritten, but requires the
author to mark that they know that they are overwriting tests, and that
it's intentional.
The error message will compare the tests by command, if the two tests
have different commands then the commands will be printed for easy
visual comparison. This helps to identify whether a test is being added
twice (in a loop for example) or if two different tests are being
assigned the same name.
This also adds some tests for TestDict.
v2: - remove some rebase artifacts, this makes the code a little simpler
and a little cleaner
v3: - rebase on master, includes grouptools separator changes
v4: - Use a incremented value instead of True false for the context
manager, this allows the allow_reassignment contextmanager to be
nested. (Ilia)
v5: - Add comparison methods to the Test class
- Use said comparisons to make the error reporting more verbose
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu> (v4)
|
|
This test is exactly the same as another test added a few lines later.
v2: - add this patch
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
Because gs is a 1.50 features, but is added in the 1.30 and 1.40 loops
it currently adds the same tests twice. This corrects that.
NOTE: Ilia and I aren't sure this is 100% correct, but it doesn't change
the current behavior.
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
Same as previous patch.
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
This doesn't actually effect the nature or number of tests run.
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
This test was added twice, remove the second copy.
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
I traced these two tests back through git history, and through a series
of errors an option required to make them unique was dropped, this
corrects that and brings them back to their original state.
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
fp-indirections takes several minutes to run on my laptop, and it
doesn't even test anything useful on modern hardware. Just skip it when
the driver exposes a value which basically means "I don't have a limit
for you to test."
Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
Reviewed-by: Matt Turner <mattst88@gmail.com>
|
|
Fixes list for compressedtextureimage.
Trivial.
Reviewed-by: Dylan Baker <baker.dylan.c@gmail.com>
|
|
arb_direct_state_access-compressedtextureimage should use a more mainstream
compression format in all.py. This patch changes it to
GL_COMPRESSED_RGBA_S3TC_DXT5_EXT.
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
Signed-off-by: Anuj Phogat <anuj.phogat@gmail.com>
Reviewed-by: Chris Forbes <chrisf@ijw.co.nz>
|
|
Test try_opt_frontfacing_ternary optimization when type is vec4,
this test fails with current Mesa HEAD (ce83a6e).
Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
Reviewed-by: Matt Turner <mattst88@gmail.com>
|
|
Fixes failures on OCL-1.1 implementations that provide cl_khr_fp64
Signed-off-by: Jan Vesely <jan.vesely@rutgers.edu>
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
|
|
Trivial.
|
|
From GLSL 1.50 spec, section 4.3.4 "Inputs":
"Only the input variables that are actually read need to be written by the
previous stage"
[...]
"Geometry shader input variables get the per-vertex values written
out by vertex shader output variables of the same names."
As there is not vertex shader that defines the respective output
variables, this test should fail when linking. However, as it is checking
that smooth and flat interpolation qualifiers are allowed in geometry
shaders, this patch disables link checking.
Signed-off-by: Samuel Iglesias Gonsalvez <siglesias@igalia.com>
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
Fix array sizes so that the arrays are not larger than
the minimum implementation requirement of GL_MAX_VERTEX_ATTRIBS.
Also assign something to the output so that its marked as used.
The minumum for GL_MAX_VERTEX_ATTRIBS is 64.
Reviewed-by: Chris Forbes <chrisf@ijw.co.nz>
|
|
v2: array size is 2, not 1 (Matt Turner)
This test fails with current Mesa HEAD (6264348), see bug
https://bugs.freedesktop.org/show_bug.cgi?id=84225.
Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
Reviewed-by: Matt Turner <mattst88@gmail.com>
|
|
Test results:
AMD Radeon HD 6670 - Catalyst 14.501.1003 OpenGL 4.4
interface-block-instance-name-input-read-only.frag - pass
interface-block-input-read-only.frag - pass
interface-block-instance-name-uniform-read-only.frag - fail
interface-block-uniform-read-only.frag - fail
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
Reviewed-by: Mark Janes <mark.a.janes@intel.com>
|
|
This is a rip off of:
https://www.khronos.org/registry/webgl/conformance-suites/1.0.2/conformance/attribs/gl-vertex-attrib-render.html
Which presently fails with gallium drivers. The logic is identical, just
ported to GL and piglit infra.
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
|
|
The copy propagation pass didn't properly deal with arrays, which caused
it to merge b[1] and a[1] even though a[1] is modified after the initial
assignment.
Test taken verbatim from
https://www.khronos.org/registry/webgl/conformance-suites/1.0.2/conformance/ogles/GL/functions/array_float_frag.frag
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Dave Airlie <airlied@redhat.com>
|
|
copied from atan2
tested on clover and intel ocl-sdk
Signed-off-by: Jan Vesely <jan.vesely@rutgers.edu>
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
|
|
copied from asin
tested on clover and intel ocl
Signed-off-by: Jan Vesely <jan.vesely@rutgers.edu>
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
|
|
copied from acos.
tested on clover and intel ocl
Signed-off-by: Jan Vesely <jan.vesely@rutgers.edu>
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
|
|
Don't exit during the pre-run hook if the environment check fails and
dry-run mode is enabled.
Signed-off-by: Thomas Wood <thomas.wood@intel.com>
Reviewed-by: Dylan Baker <baker.dylan.c@gmail.com>
|
|
Signed-off-by: Thomas Wood <thomas.wood@intel.com>
Reviewed-by: Dylan Baker <baker.dylan.c@gmail.com>
|
|
The ARB_draw_buffers spec allows GL_MAX_DRAW_BUFFERS == 1, which means
that our GL_COLOR_ATTACHMENT1 usage will throw a GL error.
Fixes ARB_color_buffer_float/GL_RGBA8-queries on VC4.
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
|
|
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
|
|
|
|
48 of the generated tests were linker-error failing on vc4 due to
trying to use too many varying components.
|
|
Manually running the command 4 times every time you want to touch the
scripts is terrible.
|
|
|
|
I was going to have to copy/paste the same code for varying components.
|
|
The textureProj tests multiply expected texture coordinates by the projector
in advance so that when the driver does the division we obtain the same
coordinates. However, the division can lead to small rounding errors that
can affect the selected layer and fail the tests. This is currently happening
on Intel hardware for all projector tests involving 3D textures.
When we test a 3D texture for texture level 0 we have 32 layers, which
means that each layer takes 1/32 = 0.03125 space in the [0, 1] texture
coordinate space. The test uses 0.5 for the Z coordinate, which is exactly
the boundary between layers 15 and 16 (16 * 0.03125 = 0.5). Because we
first multiply 0.5 by the projector in CPU and then we divide the coordinate
by the driver in the GPU, the result may be subject to rounding/precision
errors and if the result of this operation is even slighly smaller than 0.5
the hardware will select layer 15 instead of layer 16, leading to the
test failures we currently see, at least on Intel hardware, for all piglit
tests that involve textureProj with 3D textures.
The patch prevents this rounding from affecting the result of the test by
using 0.51 as the target texture coordinates instead of 0.5. Because 0.51
is 0.01 into layer 16, we are giving a small room for rounding/precision
errors that won't lead the hardware to select a different layer.
This fixes all projector tests on Intel hardware:
bin/tex-miplevel-selection *ProjGradARB 3D -fbo -auto
bin/tex-miplevel-selection *ProjLod 3D -fbo -auto
bin/tex-miplevel-selection textureProj 3D -fbo -auto
bin/tex-miplevel-selection textureProjGrad 3D -fbo -auto
bin/tex-miplevel-selection textureProjGradOffset 3D -fbo -auto
bin/tex-miplevel-selection textureProjOffset 3D -fbo -auto
bin/tex-miplevel-selection "textureProj(bias)" 3D -fbo -auto
bin/tex-miplevel-selection "textureProjOffset(bias)" 3D -fbo -auto
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=81405
|
|
Fix Clang unused-const-variable warnings.
gettransformfeedback.c:84:22: warning: unused variable 'out1_ret' [-Wunused-const-variable]
static const GLfloat out1_ret[NUM_INPUTS] = { 0.0, 1.0, 2.0, 4.0};
^
gettransformfeedback.c:85:22: warning: unused variable 'out2_ret' [-Wunused-const-variable]
static const GLfloat out2_ret[NUM_INPUTS] = {-2.0, 0.0, 2.0, 6.0};
^
Signed-off-by: Vinson Lee <vlee@freedesktop.org>
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
fs-discard-exit-2.c:118:13: warning: using floating point absolute value function 'fabs' when argument is of integer type [-Wabsolute-value]
int dx = fabs(sx - x / 8);
^
fs-discard-exit-2.c:118:13: note: use function 'abs' instead
int dx = fabs(sx - x / 8);
^~~~
abs
fs-discard-exit-2.c:119:13: warning: using floating point absolute value function 'fabs' when argument is of integer type [-Wabsolute-value]
int dy = fabs(sy - y / 8);
^
fs-discard-exit-2.c:119:13: note: use function 'abs' instead
int dy = fabs(sy - y / 8);
^~~~
abs
Signed-off-by: Vinson Lee <vlee@freedesktop.org>
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
Fix out-of-bounds read defect reported by Coverity.
Signed-off-by: Vinson Lee <vlee@freedesktop.org>
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
Silence unchecked return value from library defect reported by Coverity.
Signed-off-by: Vinson Lee <vlee@freedesktop.org>
Reviewed-by: Brian Paul <brianp@vmware.com>
|
