generators: port variable-index-read.sh to python

This patch replaces a bash based generator with a python generator. This
has the obvious advantage of remove a large swath of generated tests
from the check-in, and prevents modification of a generated file. It
also is much faster than the bash generator, so running at compile time
isn't a problem.

There are no functional differences between the bash generated versions
and the python generated versions, only whitespace/line-wrapping
differences, and small changes to the copyright header.

All tests that passed with the bash versions pass with the python
versions on the i965 driver with multiple hardware revisions.

Tested with python2.7 and python3.3

v2: - rename generated test .list file (Emil)
    - Use a shared function to add the license text
      (also removes a typo in the text spotted by Emil)

Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Acked-by: Jose Fonseca <jfonseca@vmware.com>

1 files changed, 0 insertions, 70 deletions

diff --git a/tests/spec/glsl-1.10/execution/variable-indexing/vs-varying-array-mat3-col-rd.shader_test b/tests/spec/glsl-1.10/execution/variable-indexing/vs-varying-array-mat3-col-rd.shader_test
deleted file mode 100644
index 4abf62664..000000000
--- a/tests/spec/glsl-1.10/execution/variable-indexing/vs-varying-array-mat3-col-rd.shader_test
+++ /dev/null
@@ -1,70 +0,0 @@
-# Test generated by:
-# ../../../glsl-1.10/variable-index-read.sh 1.10
-
-[require]
-GLSL >= 1.10
-GL_MAX_VARYING_COMPONENTS >= 31
-
-[vertex shader]
-uniform int col;
-uniform vec3 expect;
-varying mat3 m[3];
-varying vec4 color;
-
-void main()
-{
-    gl_Position = gl_ModelViewProjectionMatrix * gl_Vertex;
-
-    m[0] = mat3(1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0);
-    m[1] = mat3(10.0, 11.0, 12.0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0);
-    m[2] = mat3(19.0, 20.0, 21.0, 22.0, 23.0, 24.0, 25.0, 26.0, 27.0);
-
-    /* From page 23 (page 30 of the PDF) of the GLSL 1.10 spec:
-     *
-     *     "A vertex shader may also read varying variables, getting back the
-     *     same values it has written. Reading a varying variable in a vertex
-     *     shader returns undefined values if it is read before being
-     *     written."
-     */
-    color = (m[1][col] == expect)
-        ? vec4(0.0, 1.0, 0.0, 1.0) : vec4(1.0, 0.0, 0.0, 1.0);
-}
-
-[fragment shader]
-uniform int col;
-uniform vec3 expect;
-varying mat3 m[3];
-varying vec4 color;
-
-void main()
-{
-    /* There is some trickery here.  The fragment shader has to actually use
-     * the varyings generated by the vertex shader, or the compiler (more
-     * likely the linker) might demote the varying outputs to just be vertex
-     * shader global variables.  Since the point of the test is the vertex
-     * shader reading from a varying, that would defeat the test.
-     */
-    gl_FragColor = (m[1][col] == expect)
-        ? color : vec4(1.0, 0.0, 0.0, 1.0);
-}
-
-[test]
-clear color 0.5 0.5 0.5 0.5
-clear
-ortho
-
-uniform int col 0
-uniform vec3 expect 10 11 12
-draw rect 60 5 10 10
-probe rgb 65 10 0.0 1.0 0.0
-
-uniform int col 1
-uniform vec3 expect 13 14 15
-draw rect 75 5 10 10
-probe rgb 80 10 0.0 1.0 0.0
-
-uniform int col 2
-uniform vec3 expect 16 17 18
-draw rect 90 5 10 10
-probe rgb 95 10 0.0 1.0 0.0
-