MESA_DEBUG=incomplete_tex prints warnings from glClear which doesn't use the state
@glennk
Submitted by Glenn Kennard Assigned to mes..@..op.org
Description
Reproducible by running the arb_texture_view-sampling-2d-array-as-2d-layer piglit test case, the first call to glClear ends up checking the currently bound shader's state for texture completeness and prints the following warning: Mesa: Texture Obj 0 incomplete because: Image[baseLevel=0] == NULL
As far as I can tell this is due to _mesa_Clear calling _mesa_update_state which eventually gets to _mesa_test_texobj_completeness where the warning is printed.
Checking texture completeness in glClear strikes me as rather odd, in particular since the check is on the api bound shader, not the internal state used for the clear itself.
Version: git