[Piglit] [PATCH] piglit-dispatch: update gl.spec, gl.tm and enumext.spec from the registry
eric at anholt.net
Wed Jan 30 13:23:59 PST 2013
Paul Berry <stereotype441 at gmail.com> writes:
> On 29 January 2013 09:48, Christoph Bumiller <christoph.bumiller at speed.at>wrote:
>> On 29.01.2013 16:55, Tom Gall wrote:
>> > Hi Christoph,
>> > If you look at the bottom of http://www.opengl.org/registry/ you will
>> > enum.spec - canonical description of the reserved OpenGL enumerants
>> > and the ranges allocated for different purposes. New allocations are
>> > made here and when extensions using values in allocated ranges are
>> > registered, the enumerants in those extensions are added as well.
>> > enumext.spec - derived variant of enum.spec containing the enumerant
>> > values grouped by the extension or API core revision they correspond
>> > to.
>> > gl.spec - canonical description of the functions defined by core
>> > OpenGL and extensions. When extensions are registered, the functions
>> > they define are added here.
>> > gl.tm - typemap used to convert the abstract typenames in gl.spec into
>> > underlying GL types.
>> > enumext.spec, gl.spec, and gl.tm are used to generate glext.h
>> > Is that where you obtained your proposed update from ?
>> Sure, that seemed like the most official source, but as you can see
>> those files are slighlty defective ...
> Yes, and Piglit has acquired a few corrections to them (see in particular
> commits 6409a67 and e9db1f0). Unfortunately Christoph's patch un-does
> several of those corrections.
> I've posted a revised version of the patch to branch "dispatch-update" of
> git://github.com/stereotype441/piglit.git which I believe is correct.
> Christoph and/or Tom--would you mind having a look to see if it looks right
> to you? If so let me know and I'll push it to master.
> Keeping Piglit's modified versions of these files up to date with the
> versions posted on OpenGL's web site has proven to be a bit of a nightmare,
> and I'm working on a new system that should make things a lot easier (see
> http://lists.freedesktop.org/archives/piglit/2013-January/004442.html for a
> summary of my plans). Unfortunately those plans got put on hold for about
> a month as the Intel folks were focusing on implementing GLES 3.0.
> Hopefully I will be able to return to that work next week.
If we actually made use of git branches for merging upstream code into
our modified version, it should be a lot easier. I did it with glean
for a long time.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the Piglit