https://bugs.freedesktop.org/show_bug.cgi?id=92783
Bug ID: 92783
Summary: MESA_DEBUG=incomplete_tex prints warnings from glClear
which doesn't use the state
Product: Mesa
Version: git
Hardware: All
OS: All
Status: NEW
Severity: minor
Priority: low
Component: Mesa core
Assignee: mesa-dev@lists.freedesktop.org
Reporter: glenn.kenn...@gmail.com
QA Contact: mesa-dev@lists.freedesktop.org
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
