Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
This doesn't test repeated copies with TextureBarrier()s in between,
but that doesn't seem like important new behavior in this extension.
|
|
Fixes failure on vc5 where the alpha was forced to 1 due to an rgbx
window system buffer.
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
|
|
|
|
|
|
|
|
I don't think this has been used in years -- khr_gles is the closest
thing to how you'd run the conformance tests under piglit, today.
|
|
|
|
|
|
|
|
|
|
Besides code removal, this fixes behavior if test_format was to return
PIGLIT_WARN on some tests but not others.
|
|
When I published trace-db, I decided to rename vc4 to mention "v3d",
but failed to catch the driver classifier up.
|
|
|
|
There's a limitation on VC4 where it can only handle 65536 verts at a
time in a glDrawArrays(), so the driver needs to split up the calls.
This tests that path for all the primitive types.
|
|
|
|
|
|
In a12310df3bdd0a we realized that
intel_conservative_rasterization-invalid_gles3 was not added to the
test list. Turns out we didn't even run this test on gles.
Although quite a few cases are opengl specific, there are still 2
invalid cases we can verify on gles.
Fixes: a12310df3bdd0a ("tests/opengl: Add intel_conservative_rasterization-invalid_gles3")
Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Reviewed-by: Dylan Baker <dylan@pnwbakers.com>
|
|
|
|
Fixes: 6ed37e5d2a58d36b4b04b09f8c069f2dbcff1968
("Add nv_image_formats tests")
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
|
|
Fixes: ed153b51b57762e43d44e8f49dbe9bf0422e1400
("Add GL_INTEL_conservative_rasterization tests")
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
|
|
Fixes: 2a7047a32bb3a9a4fad5bea0a8185d63af6bddf3
("glx: Introduce a glx-swap-copy test v2")
CC: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
Fixes: ce69a7afc5eb4c6a3093d0bdd9a66f51444bd07a
("Test that if VertexAttribPointer uses a packed type, size must be 4 or BGRA.")
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
Fixes: bcaa0cd75fd7b1d35817792b4802cce5eb47754d
("Test that VertexAttribP*() must use one of the appropriate types.")
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
These were converted to work with oes_texture_view, but never added to
all.py (now opengl.py)
Fixes: cde860ab32511812ecbf1d8b8d97f192273457a1
("arb_texture_view: convert some more tests to run on ES 3.1")
CC: Tapani Pälli <tapani.palli@intel.com>
|
|
Originally sanity was billed as a sort of "check if the installation
works" sort of profile. No one seems to use sanity at all, so we'd like
to re-purpose it (a little) to be a sort of "driver sanity" check, in
other words, a minimal number of tests that are able to touch a broad
swath of OpenGL features.
Some of the things this touches now:
- vertex shaders
- fragment shaders
- geometry shaders
- tesselation shaders
- compute shaders
- transform feedback
- ssbos
- atomics
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
|
|
|
|
argument
The saturate version hits an assertion failure in the Mesa i965 driver:
src/intel/compiler/brw_fs.cpp:2377: bool fs_visitor::opt_algebraic(): Assertion `!"unimplemented: saturate mixed types"' failed.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Timothy Arceri <tarceri@itsqueeze.com>
|
|
The fsign(-abs(x)) tests tickle a bug in the Mesa i965 fs backend that
was found by inspection. All of the abs() versions hit problems in the
i965 vec4 backend.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Timothy Arceri <tarceri@itsqueeze.com>
|
|
|
|
This change also splits apart some of the compute test common
functions to make them easier to use with display lists.
I submitted a spec bug and it was decided the indirect dispatch
should generate an error when called during display list
compilation.
Acked-by: Marek Olšák <marek.olsak@amd.com>
|
|
This allows an timeout (in integers) to be set for each test. If the
tests run over this alotted time they'll be killed and the status will
be set to timeout. This only work on Unix-like machines running with
python 3.x or with 2.7 and subprocess32 installed.
It can be made to work for windows, either by bumping the python version
or by writing some windows specific code for killing processes.
v2: - Add the word "Default" to help message.
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
|
|
v2: EXT_render_snorm does not add new formats for glTexBuffer,
add separate flag to indicate glTexBuffer support (separate
from req_render that matched before)
Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
|
|
Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
Reviewed-by: Timothy Arceri <tarceri@itsqueeze.com>
Reviewed-by: Dylan Baker <dylan@pnwbakers.com>
|
|
None of our other tests for instanced geometry shaders transfered
the vertices to the geometry shader from the vertex shader via
gl_Position.
This used to be broken with the i965 driver's in Mesa 12.1.0
on revision d10ae20b9678f1a5b8a81716c68e612662665277.
Signed-off-by: Andrii Simiklit <andrii.simiklit@globallogic.com>
Reviewed-by: Timothy Arceri <tarceri@itsqueeze.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96354
|
|
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
|
|
From the ARB_draw_indirect spec:
"Initially zero is bound to DRAW_INDIRECT_BUFFER. In the
compatibility profile, this indicates that DrawArraysIndirect and
DrawElementsIndirect are to source their arguments directly from the
pointer passed as their <indirect> parameters."
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
We weren't really testing that the displays list worked since
the calls could have just been executed immediately.
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
|
|
The issuses section of GL_NV_fog_distance says:
How does this extension interact with the EXT_fog_coord extension?
If FOG_COORDINATE_SOURCE_EXT is set to FOG_COORDINATE_EXT, then
the fog distance mode is ignored. However, the fog distance
mode is used when the FOG_COORDINATE_SOURCE_EXT is set to
FRAGMENT_DEPTH_EXT. Essentially, when the EXT_fog_coord
functionality is enabled, the fog distance is supplied by the
user-supplied fog-coordinate so no automatic fog distance
computation is performed.
A heavily modified version of this test passes on a Geforce3 (NV20)
running NVIDIA's 71.86.15 drivers. These are the last drivers that
support NV10 through NV2x, and they are shipped in 2011.
v2: Use piglit_draw_rect_z and fix a space-before-tab problem. Both
suggested by Eric.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
|
|
A heavily modified version of this test passes on a Geforce3 (NV20)
running NVIDIA's 71.86.15 drivers. These are the last drivers that
support NV10 through NV2x, and they are shipped in 2011.
v2: Use piglit_draw_rect_z instead of the VBO complexity. Cuts about 80
lines of code. Suggested by Eric.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Acked-by: Eric Anholt <eric@anholt.net>
|
|
v2: Explicitly use GL_NO_ERROR instead of expected_error in the
'piglit_is_extension_supported("GL_NV_fog_distance") &&
!piglit_is_extension_supported("GL_SGIS_fog_function")' block. Based on
conversation with Eric.
v3: Add some missing newlines in printfs. This caused the CI to show
"Incomplete run" instead of pass.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
num_operators_rgb and num_operators_a always have the same value, so
just use one variable.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
EXT_blend_minmax
And vice versa.
v2: Elimintate the static arrays used to populate operators[]. This
simplifies the code a lot. Suggested by Eric.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
There were two bugs here. First, GL_EXT_blend_color and
GL_EXT_blend_func_separate were only tested if the version is 1.4. This
is unnecessary because those extensions are part of OpenGL 1.4. Second,
GL_EXT_blend_minmax was typoed GL_EXT_blend_min_max.
Increases the number of subtests on RV250 (which supports OpenGL 1.3,
GL_EXT_blend_subtract, GL_EXT_blend_minmax, GL_EXT_blend_color,
GL_EXT_blend_func_separate, and GL_EXT_blend_equation_separate) from 72
to 27,552. This is the same number of tests that run on Broadwell
(which supports OpenGL 4.5). R100, NV10, NV20, and i830 should also see
the number of subtests increase.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
This is a bit odd, there seems to be support in the test for running
with ARB_ES3_compatibility and there are entries in opengl.py for the GL
versions, but no cmake was added.
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
This has never existed, it was added by mistake when the format of
all.py was changed.
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
|
|
These are all wrong, the last line does nothing since there aren't
enough arguments and always skips, the loop doesn't work since it points
at a non-existent binary.
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
|