[Bug 98250] dEQP-GLES31.functional.debug.negative_coverage.get_error.texture.texparameterIiv/texparameterIuiv failure

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=98250

Samuel Iglesias <siglesias at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTOURBUG

--- Comment #1 from Samuel Iglesias <siglesias at igalia.com> ---
Notice that this subtest is expecting an OpenGL ES 3.2 context to run, so that
can be confusing as, in OpenGL ES 3.1, GL_TEXTURE_BORDER_COLOR is not allowed
in  glTexParameterI{i,ui}v(). See file
modules/gles31/functional/es31fNegativeTextureApiTests.cpp, function
texparameterIiv().

However in OpenGL ES 3.2, glTexParameterI{i,ui}v() called with
GL_TEXTURE_BORDER_COLOR pname accepts any 4 values. See OpenGL ES 3.2 spec,
section 8.10 "Texture Parameters".

The test is passing an array of 2 values as argument and expects the driver to
detect that it is invalid. Nevertheless, the argument is a pointer to the array
and the driver, internally, will pick 4 values reading the rest from the stack
and it cannot know that the user gave less values than expected.

I submitted a patch for dEQP:

https://android-review.googlesource.com/299257

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20161103/748e6546/attachment-0001.html>