[Mesa-dev] [shader-db PATCH 1/5] run: create debug contexts

[Ilia Mirkin]

On Thu, Dec 31, 2015 at 12:17 PM, Matt Turner <mattst88 at gmail.com> wrote:
> On Thu, Dec 31, 2015 at 9:45 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
>> On Dec 31, 2015 9:32 AM, "Matt Turner" <mattst88 at gmail.com> wrote:
>>>
>>> On Wed, Dec 30, 2015 at 9:32 PM, Nicolai Hähnle <nhaehnle at gmail.com>
>>> wrote:
>>> > For Gallium-based drivers, this is required for receiving shader
>>> > information
>>> > via debug messages.
>>> > ---
>>>
>>> But that's a Gallium bug, right?
>>>
>>> Ilia sent a similar patch, and in the discussion I think we decided
>>> that what run.c is doing is perfectly fine.
>>
>> It's not a bug at all. Behavioural difference from i965 though. I was happy
>> to let the matter drop as I was the sole user of it. Sounds like there are
>> going to be more now, so this has to be addressed one way or the other.
>
> Could you summarize what that difference is?

Sure. i965 always generates messages to be sent to KHR_debug
(potentially restricted by some env vars as well). st/mesa only passes
the callback info through for GL debug contexts. The drivers, in turn,
can use the presence/absence of the callback as an indicator as to
whether to perform extra work. Mildly relatedly, currently GL context
flags are not made available in pipe contexts.

  -ilia