diff options
author | Alejandro Piñeiro <apinheiro@igalia.com> | 2015-12-15 20:08:14 +0100 |
---|---|---|
committer | Alejandro Piñeiro <apinheiro@igalia.com> | 2016-03-04 09:18:56 +0100 |
commit | 98906d0acbcff43fcfa93041bba423feeae9e00a (patch) | |
tree | fdc40129520ccaa768085b2875901dd253956ac5 /tests/all.py | |
parent | 4cbf29e75349949ea86a7870a5169afdb5a88e5a (diff) |
arb_internalformat_query2: max dimensions related checks
Add a check for the following pnames (a subtest for each one)
* MAX_WIDTH. From spec:
"The maximum supported width for the resource is returned in
<params>. For resources with only one-dimension, this one
dimension is considered the width. If the resource is unsupported,
zero is returned."
It is only tested that returns zero if not supported. It makes
sense to include it on this test because it is related to the
other max dimension pnames.
* MAX_HEIGHT. From spec:
"The maximum supported height for the resource is returned in
<params>. For resources with two or more dimensions, the second
dimension is considered the height. If the resource does not have
at least two dimensions, or if the resource is unsupported, zero
is returned."
So in addition to the usual zero-test if not supported, it is tested
that if the target has less that two dimensions, it returns zero
too, even if supported.
* MAX_DEPTH: From spec:
"The maximum supported depth for the resource is returned in
<params>. For resources with three or more dimensions, the third
dimension is considered the depth. If the resource does not have
at least three dimensions, or if the resource is unsupported, zero
is returned.
So in addition to the usual zero-test if not supported, it is tested
that if the target has less that three dimensions, it returns zero
too, even if supported.
* MAX_LAYERS: From spec:
"The maximum supported number of layers for the resource is
returned in <params>. For 1D array targets, the value returned is
the same as the MAX_HEIGHT. For 2D and cube array targets, the
value returned is the same as the MAX_DEPTH. If the resource does
not support layers, or if the resource is unsupported, zero is
returned."
In addition to the usual zero-test if not supported, it is tested
that the value returned is the same that the one returned by
MAX_HEIGHT or MAX_DEPTH for the array texture targets.
Tested on NVIDIA GeForce GTX 950 - NVIDIA 352.55: passes.
Tested on 4.5.13399 on AMD Radeon (TM) R9 380 Series: the tests
doesn't pass for this ATI proprietary drivers for any of the
subtests. It returns a non-zero value for unsupported combinations.
Acked-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'tests/all.py')
-rw-r--r-- | tests/all.py | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/all.py b/tests/all.py index 9f1f13382..636c985e8 100644 --- a/tests/all.py +++ b/tests/all.py @@ -3670,6 +3670,7 @@ with profile.group_manager( g(['arb_internalformat_query2-internalformat-size-checks'], 'All INTERNALFORMAT_<X>_SIZE pname checks') g(['arb_internalformat_query2-internalformat-type-checks'], 'All INTERNALFORMAT_<X>_TYPE pname checks') g(['arb_internalformat_query2-image-format-compatibility-type'], 'IMAGE_FORMAT_COMPATIBILITY_TYPE pname checks') + g(['arb_internalformat_query2-max-dimensions'], 'Max dimensions related pname checks') with profile.group_manager( PiglitGLTest, grouptools.join('spec', 'arb_map_buffer_range')) as g: |