[Mesa-dev] [PATCH] mesa: Add ARB_separate_shader_objects to dispatch_sanity

[Ian Romanick]

On 05/28/2013 12:31 PM, Matt Turner wrote:
> On Tue, May 28, 2013 at 11:26 AM, Ian Romanick <idr at freedesktop.org> wrote:
>> -// { "glValidateProgramPipeline", 43, -1 },             // XXX: Add to xml
>> -// { "glGetProgramPipelineInfoLog", 43, -1 },           // XXX: Add to xml
>> +   { "glValidateProgramPipeline", 43, -1 },
>> +   { "glGetProgramPipelineInfoLog", 43, -1 },
>
> Could you explain to me why these are 43s (rather than 41) again? I
> thought (and from looking at the rest of the file, this seems to be
> the case) that they were the minimum context version that guarantees
> the functions' availability, either by GL spec requirements of or
> "every driver that supports X.Y has this function). I filed bug 62612
> to get this sorted but there was some misunderstanding somewhere.

I honestly have no idea.  I objected to this whole mechanism for 
separating functions by version when Jordan first proposed it.  What I 
wanted (and what would have been understandable!) is for there to be a 
separate table for each version that contains the functions that Mesa 
can support starting with that version.  This is the way the ES2 vs ES3 
is handled.  The current setup is just lies... there are quite a few 
OpenGL 3.0 functions that Mesa can support in OpenGL 1.4 contexts (via 
extensions).