diff options
author | Roland Scheidegger <[email protected]> | 2018-01-27 01:39:35 +0100 |
---|---|---|
committer | Roland Scheidegger <[email protected]> | 2018-01-30 01:28:47 +0100 |
commit | 3c7aa242f5df6ba45acc7338bad088910e4b7330 (patch) | |
tree | c4d91dbf901de3c8dd2a90cceb0d18df1bada88a /src/gallium/drivers/radeon/radeon_vcn_enc.h | |
parent | 21fe02d1d369d25021d0be7f558063e103e2dce7 (diff) |
mesa: skip validation of legality of size/type queries for format queries
The size/type query is always legal (if we made it that far).
Removing this causes a difference for GL_TEXTURE_BUFFER - the reason is that
these parameters are valid only with GetTexLevelParameter() if gl 3.1 is
supported, but not if only ARB_texture_buffer_object is supported.
However, while the spec says that these queries return "the same information
as querying GetTexLevelParameter" I believe we're not expected to return just
zeros here. By definition, these pnames are always valid (unlike for the
GetTexLevelParameter() function which would return an error without GL 3.1).
The spec is a bit inconsistent there and open to interpretation - while
mentioning the "same information as querying GetTexLevelParameter" is
returned, it also mentions that 0 is returned for size/type if the
target/format is not supported - implying correct results to be returned
if it is supported, regardless that GetTexLevelParameter would return
an error. (Also, the bit about this returning the same as
GetTexLevelParameter also includes querying stencil type, which isn't
even possible with GetTexLevelParameter.)
This breaks some piglit arb_internalformat_query2 tests (which I believe to
be wrong).
Reviewed-by: Alejandro Piñeiro <[email protected]>§
Diffstat (limited to 'src/gallium/drivers/radeon/radeon_vcn_enc.h')
0 files changed, 0 insertions, 0 deletions