mesa: Report core FBO incompleteness cases through GL_ARB_debug_output.
authorEric Anholt <eric@anholt.net>
Thu, 6 Jun 2013 18:13:02 +0000 (11:13 -0700)
committerEric Anholt <eric@anholt.net>
Fri, 7 Jun 2013 23:05:42 +0000 (16:05 -0700)
commit3c21a7d3c9b626a10a38987d77b9e77d70bd67d7
tree8136166c8b27222afca1fbf2518459c378eebecc
parent9e3475b39ae34244045e0dcd6b98e1526c10c6bf
mesa: Report core FBO incompleteness cases through GL_ARB_debug_output.

Just like we produce from inside the Intel driver, this can help provide
information quickly about FBO incompatibility problems (particularly when
using apitrace replay).

Currently, in driver-marked incompleteness cases, you'll get both the
driver message and the core message on Intel.  Until the other drivers are
fixed to produce output, I think this is better than not putting in a
message for driver-marked incomplete.

Reviewed-by: Brian Paul <brianp@vmware.com>
src/mesa/main/fbobject.c