GS: Test that geometry ins/outs can have flat/smooth/noperspective qualifiers

v2: Modify test to also test for correct interpolation of data being passed

Reviewed-by: Paul Berry <stereotype441@gmail.com>
GS: Tests that varying arrays can only be passed between VS and GS within blocks

v2: Fix comments and also modify vs-gs-arrays-within-blocks-pass.shader_test
so that all vertices have different values to be checked

Reviewed-by: Paul Berry <stereotype441@gmail.com>
GS: Test that varyings of the same name between VS and GS must match types

Reviewed-by: Paul Berry <stereotype441@gmail.com>
GS: Test that EndPrimitive() is optional for geometry output layout of "points"

Reviewed-by: Paul Berry <stereotype441@gmail.com>
Test that invariant qualifier is available to all shaders

 GLSL 1.50 section 4.6.1 (The Invariant Qualifier) says:
   To ensure that a particular output variable is invariant, it is necessary
   to use the invariant qualifier. It can either be used to qualify a
   previously declared variable as being invariant
       invariant gl_Position; // make existing gl_Position be invariant
       out vec3 Color; // make existing Color be invariant
       invariant Color;
   or as part of a declaration when a variable is declared
       invariant centroid out vec3 Color;
   The invariant qualifier must appear before any interpolation qualifiers or
   storage qualifiers when combined with a declaration. Only variables output
   from a shader (including those that are then input to a subsequent shader)
   can be candidates for invariance. This includes user-defined output variables
   and the built-in output variables. For variables leaving one shader and coming
   into another shader, the invariant keyword has to be used in both shaders,
   or a link error will result.

v2 (Paul Berry <stereotype441@gmail.com): Add missing write to
extra01.

Reviewed-by: Paul Berry <stereotype441@gmail.com>
GLSL: Test that input layout qualifiers cannot be used on variable declarations

Reviewed-by: Paul Berry <stereotype441@gmail.com>
khr_debug: Do not use dynamically sized arrays.

This patch fixes MSVC build errors introduced with commit
6a1250d27ee56afdddf532afe3edbc4e436355c7.

debug-object-label.c
debug-object-label.c(49) : error C2057: expected constant expression
debug-object-label.c(49) : error C2466: cannot allocate an array of constant size 0
debug-object-label.c(49) : error C2133: 'label' : unknown size
debug-object-label.c(112) : error C2057: expected constant expression
debug-object-label.c(112) : error C2466: cannot allocate an array of constant size 0
debug-object-label.c(112) : error C2133: 'length' : unknown size
debug-object-label.c(113) : error C2057: expected constant expression
debug-object-label.c(113) : error C2466: cannot allocate an array of constant size 0
debug-object-label.c(113) : error C2087: 'label' : missing subscript
debug-object-label.c(113) : error C2133: 'label' : unknown size
debug-object-label.c(282) : error C2057: expected constant expression
debug-object-label.c(282) : error C2466: cannot allocate an array of constant size 0
debug-object-label.c(282) : error C2133: 'label' : unknown size
debug-object-label.c(368) : error C2057: expected constant expression
debug-object-label.c(368) : error C2466: cannot allocate an array of constant size 0
debug-object-label.c(368) : error C2133: 'buffers' : unknown size
debug-object-label.c(370) : error C2057: expected constant expression
debug-object-label.c(370) : error C2466: cannot allocate an array of constant size 0
debug-object-label.c(370) : error C2133: 'label' : unknown size

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=70248
Signed-off-by: Vinson Lee <vlee@freedesktop.org>
piglit: silence piglit_report_subtest_result() format warnings

silences a bunch of warnings such as:
"tests/fbo/fbo-alphatest-formats.c:184:3: warning: format not
a string literal and no format arguments [-Wformat-security]"
fbo-gl_pointcoord: clean up shader formatting
glean: silence unused var compiler warning
layered-2d-texture-render: add const qualifiers to silence warnings
max-texture-size: improve error message info
gs: Don't try to use gl_PerVertex when redeclaring fragment shader inputs.

In commit 5b1dff3 (Geometry shaders: Test gl_ClipDistance input (GLSL
1.50)) I accidentally used this syntax to redeclare the
gl_ClipDistance fragment shader input:

    in gl_PerVertex {
      float gl_ClipDistance[8];
    };

This is incorrect--gl_PerVertex is only meaningful in vertex and
geometry shaders.  In fragment shaders gl_ClipDistance isn't in any
interface block.

v2: don't forget the "in" keyword.
Test that struct names may not begin with "gl_" prefix.
Test illegal usages of "gl_" prefix in interface blocks.
Test that redeclaration of gl_PerVertex must be for a subset.
Test that interface blocks cannot declare conflicting names.
Test that in general, interface blocks cannot be redeclared.
Test that the built-in gl_PerVertex interface block can be redeclared.
Test that gl_PerVertex can't be redeclared after it's been used.