mesa: Track per-stage shader input and output limits independently
authorIan Romanick <ian.d.romanick@intel.com>
Tue, 10 Sep 2013 14:21:56 +0000 (09:21 -0500)
committerIan Romanick <ian.d.romanick@intel.com>
Thu, 19 Sep 2013 21:29:43 +0000 (16:29 -0500)
commita384238c3dbcc89f7acc51027b123e50d2d3ae60
tree7de9eb1d948c15c6d744b6c6e32b32e1ce03fc5a
parentd38765f3c8fbd473b949177cc9698b2cd459902c
mesa: Track per-stage shader input and output limits independently

In OpenGL 3.2 these are independently queryable.  In addition, the spec
has different minimum-maximums for various values.
GL_MAX_VERTEX_OUTPUT_COMPONENTS is 64, but
GL_MAX_GEOMETRY_OUTPUT_COMPONENTS (and GL_MAX_FRAGMENT_INPUT_COMPONENTS)
is 128.

In OpenGL ES 3.0 these are also independently queryable.  The spec has
different minimum-maximums for various values.
GL_MAX_VERTEX_OUTPUT_VECTORS is 16, but GL_MAX_FRAGMENT_INTPUT_VECTORS
is 15.

None of these values are used yet.  I have just added space to the
structures.  Future patches will add users and eventually remove some
old fields.

Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
Reviewed-by: Brian Paul <brianp@vmware.com>
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
Reviewed-by: Paul Berry <stereotype441@gmail.com>
Cc: Zack Rusin <zackr@vmware.com>
src/mesa/main/mtypes.h