Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
|
|
Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
|
|
Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
|
|
Test is based on egl-create-pbuffer-surface but tests that using
EGL_LARGEST_PBUFFER attribute works as specified
Test fails on current Mesa and Nvidia binary driver version 355.11.
v2: code cleanups
Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
Reviewed-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
|
|
The test uses X11 headers so this guard is needed.
Signed-off-by: Mircea Gherzan <mircea.gherzan@intel.com>
Signed-off-by: Ben Widawsky <benjamin.widawsky@intel.com>
|
|
No GLSL version implies GLSL 1.10, but that isn't supported by
fglrx in core profiles.
This lets the tests run and fail in more interesting ways on fglrx.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
BITMAP is a wingdi.h typedef.
Also, remove another bit of leftover devel/debug code.
|
|
Reviewed-by: Jose Fonseca <jfoneca@vmware.com>
|
|
skip the test if there is no linker available
fix CL_LINKER_NOT_AVAILABLE detection by testing device one by one
print the build log in case of error
|
|
image_stage_max_images().
Fixes the arb_shader_image_load_store-max-images compute stage
subtest.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94140
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
Reported-by: Mark Janes <mark.a.janes@intel.com>
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
Demonstrates a bug in Intel color resolve logic. If rendering to
texture is preceded by fast clear subsequent reads from the
texture require the underlying color buffer to be resolved. In
case of mipmap generation Intel driver needs to reallocate the
underlying buffer to fit the subsequent levels. However, copy of
the original level zero to newly allocated buffer is delayed until
the driver is about to generate level one using level zero as
source. This causes a color resolve of the original level zero.
Both the generation of level one and the resolve are meta
operations, and the latter will interfere with the sampler
settings of the former.
Signed-off-by: Topi Pohjolainen <topi.pohjolainen@intel.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
|
|
The test was passing a pointer to an uninitialized integer value as the
glShaderSource length parameter. This is meant to be an array
containing the length of each shader string.
Instead, just pass NULL, which makes the GL assume the strings are
null-terminated (which they are).
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93335
Reviewed-by: Mark Janes <mark.a.janes@intel.com>
|
|
layout qualifiers
From ARB_shader_image_load_store spec:
" (0) How does this extension differ from the similar
EXT_shader_image_load_store?
RESOLVED: The functionality provided by this extension is very similar
to that provided by EXT_shader_image_load_stores. There are some
functional differences.
* "size" layout qualifiers replaced with "format" qualifiers.
* Image loads aren't restricted to "1x8", "1x16", "1x32", "2x32", and
"4x32" formats. Instead, each supported image format has a layout
qualifier, and values loaded from images are converted to an
vec4/ivec4/uvec4 representation appropriate for the image format."
size4x32 was valid for EXT_shader_image_load_store. That explains
why this test works properly on proprietary NVIDIA drivers, as
both extensions are supported.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93336
Reviewed-by: Tapani Pälli <tapani.palli@intel.com>
|
|
piglit_build_simple_program_multiple_shaders
From piglit_build_simple_program_multiple_shaders documentation:
/**
* Builds and links a program from optional sources, throwing
* PIGLIT_FAIL on error. The last target must be 0.
*/
So internally is already calling piglit_link_check_status, deleting
the program and reporting PIGLIT_FAIL if fails.
So it is not needed to check the link status. That would be needed
when using piglit_build_simple_program_unlinked_multiple_shaders.
Reviewed-by: Tapani Pälli <tapani.palli@intel.com>
|
|
|
|
V3: rebased, fix variable copy & paste error, update the
relink_program_created_by_glCreateShaderProgram() test to check
for linking error when in core profile and no error in compat
(Timothy).
v2: Add missing extension check for GL_ARB_transform_feedback2. Use
configure_transform_feedback_object utility function. Use
CreateShaderProgram_with_xfb utility function.
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Timothy Arceri <timothy.arceri@collabora.com>
|
|
I filled a spec bug for this as the GL Core spec seems to conflict
with the GLSL spec on this and its been confirmed that they are
not intended to be allowed.
|
|
>From Section 7.3 (PROGRAM OBJECTS) of the OpenGL 4.5 spec:
"Linking can fail for a variety of reasons as specified in the
OpenGL Shading Language Specification, as well as any of the
following reasons:
- No shader objects are attached to program."
Cc: Ian Romanick <idr@freedesktop.org>
|
|
There are two tests, the second test covers what the first
test is doing plus more, so remove the first test.
Add a check that glUseProgram doesn't generate an error when
linked program is empty.
Finally move the remaining test out of the shaders folder.
Cc: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Ian Romanick <idr@freedesktop.org>
|
|
Verifies the screen position specified by glViewport is not effected by
the GL_CLIP_ORIGIN state.
Passes with nvidia, fails with Mesa until _mesa_get_viewport_xform()
is fixed.
v2: also enable back-face culling to make sure front/back-face polygon
orientation isn't upset by the clip origin.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93813
Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
Reviewed-by: Roland Scheidegger <sroland@vmware.com>
|
|
The modern piglit convention is "ext_foo_bar-testname". This patch
renames the executables to:
arb_clip_control-clip-control
arb_clip_control-depth-precision
Arguably, the first test should be split into two separate tests that
exercise state setting/getting and rendering.
Reviewed-by: Roland Scheidegger <sroland@vmware.com>
|
|
Acked-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
Python 3 doesn't allow mixing of tabs and spaces for indent, only a
choice between one or the other. Piglit uses spaces.
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Acked-by: Jose Fonseca <jfonseca@vmware.com>
|
|
Use unicode_literals from __future__. This makes undecorated strings
(those not using and b or u prefix) into unicode instead of bytes in
python 2. This means that bytes strings need to have a b prefix now.
This also fixes a couple of unittests that broke during the transition.
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Acked-by: Jose Fonseca <jfonseca@vmware.com>
|
|
This is xrange on python 2.x and range on 3.x
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Acked-by: Jose Fonseca <jfonseca@vmware.com>
|
|
These are the three python3 like behaviors that piglit should rely on.
The only other applicable future import is unicode_literals. Although my
plan is to use unicode_literals, that will actually cause behavioral
changes in some cases, where these cause minimal changes to the code.
Piglit will not be targeting < 3.2, they are old, unsupported, and have
fewer features than 2.7.
Piglit now has division (using / as floating division, and // as integer
division), print as a function (rather than a statement), and
absolute import, which changes the way import works when there's a
conflict between a local import and a system wide one. Absolute import
makes more sense, and copies the behavior of python 3
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Acked-by: Jose Fonseca <jfonseca@vmware.com>
|
|
The gl_MaxGeometryAtomicCounters does not make sense
util we have geometry shaders. I.e. glsl version 150
is the limit for this tests.
Signed-off-by: Marta Lofstedt <marta.lofstedt@linux.intel.com>
Reviewed-by: Tapani Pälli <tapani.palli@intel.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93861
|
|
All that mesa does when releasing the shader compiler is clear its
builtins list. So make sure to use a builtin, and release the compiler
sooner, to trigger a bug in mesa.
This code sequence is hit by some core Android component.
Reported-by: Rob Herring <robh@kernel.org>
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Timothy Arceri <timothy.arceri@collabora.com>
|
|
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
Adds a test that creates a framebuffer with no attachments and sets
the default sample count to 3. It then verifies that GL_SAMPLES for
the fbo is at least 3 and GL_SAMPLE_BUFFERS is 1. It also checks the
value of gl_NumSamples in the shader by writing to an SSBO with the
value to verify that it is the same as GL_SAMPLES.
Currently using an odd sample count with no attachments triggers an
assert in the i965 driver in Mesa.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93957
Cc: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
|
|
explicit offset test
|
|
Test both MS and per-sample shaded cases. With MS, there should be no
additional invocations, while with per-sample shading, each sample
should be counted.
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Tapani Pälli <tapani.palli@intel.com>
|
|
Also test the GL_RGBA internal format because GL_RGB has less hardware
support, so GL_RGBA is likelier to actually hit the fast path.
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
Reviewed-by: Anuj Phogat <anuj.phogat@gmail.com>
|
|
All other variants (array, cube_map-array, and pbo variants) are already
running concurrently
|
|
This is similar to the texsubimage test, but checks various type and format
conversions as well as a different set of pixel unpack settings.
v2: cleanups and share some code with texsubimage
|
|
The idea is that tests can get an idea of how much precision to expect when
using these formats.
v2: clarify that min_bits is for the depth component (Ian Romanick)
|
|
This is a slightly extended variant of equal_images from texsubimage
which will also be used in the new texsubimage-unpack test.
I've decided to call it "equal" instead of "compare", since I feel that
makes the meaning of the return value more obvious.
|
|
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
In case atomic counters aren't available, this is a simpler test that
just makes sure that the width/height are properly set.
Also add tests for discard as well as changing the fb params.
Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Tapani Pälli <tapani.palli@intel.com>
|
|
fbo-extended-blend-pattern was using an implicit integer to float
conversion which isn't allowed in ESSL.
builtins program linker error checking was incorrect, do explicit link
checking instead.
Reviewed-by: Ilia Mirkin <imirkin@alum.mit.edu>
|
|
Signed-off-by: Jan Vesely <jan.vesely@rutgers.edu>
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
|
|
Deprecated features are required to be supported until they are removed.
Signed-off-by: Jan Vesely <jan.vesely@rutgers.edu>
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
|
|
Signed-off-by: Jan Vesely <jan.vesely@rutgers.edu>
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
|