glapi: Store static dispatch offsets in a separate table
authorIan Romanick <ian.d.romanick@intel.com>
Sat, 9 May 2015 01:50:11 +0000 (18:50 -0700)
committerIan Romanick <ian.d.romanick@intel.com>
Sat, 16 May 2015 03:22:26 +0000 (20:22 -0700)
commitd649fcf727bffa11a5426ebcf38f51f478664b17
treea9d96cab5b6f615ae296cce8ce945ef60c8ec7d6
parent5aaabd7630ca6fd72a3333687249574e6fcbe663
glapi: Store static dispatch offsets in a separate table

Since the set of functions with static will never change, there is no
reason to store it in the XML.  It's just one of those fields that
confuses people adding new functions.

This is split out from the rest of the series so that in-code assertions
can be used to verify that the data in the Python code matches the XML.

Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
Reviewed-by: Dylan Baker <baker.dylan.c@gmail.com>
src/mapi/glapi/gen/Makefile.am
src/mapi/glapi/gen/gl_XML.py
src/mapi/glapi/gen/static_data.py [new file with mode: 0644]