This is explicitly forbidden: Geometry shader input blocks [...]. All
other input and output block arrays must specify an array size.
The vertex and fragment shader tests pass on Mesa. The GS test has not
been tested.
Cc: Jordan Justen jljus...@gmail.com
Signed-off-by: Kenneth Graunke
On 06/07/2013 10:51 PM, Matt Turner wrote:
[snip]
Both are
Reviewed-by: Matt Turner matts...@gmail.com
Does glslparsertest test need to know about core/compatibility options
for glsl_version?
If we want to have compatibility mode tests, then yes. But since we
aren't planning on
On Sat, Jun 8, 2013, at 08:28 AM, Kenneth Graunke wrote:
This is explicitly forbidden: Geometry shader input blocks [...]. All
other input and output block arrays must specify an array size.
The vertex and fragment shader tests pass on Mesa. The GS test has not
been tested.
Cc: Jordan
The asmparsertest/shaders/ARBvp1.0/address-06.txt tests against
constant array index offset too large and expects it to fail.
Currently in mesa this does not cause the program to fail and based on
my reading of [1] this is the correct behaviour. The test uses
relative addressing for which
On 06/08/2013 03:21 AM, Fabian Bieler wrote:
On Sat, Jun 8, 2013, at 08:28 AM, Kenneth Graunke wrote:
This is explicitly forbidden: Geometry shader input blocks [...]. All
other input and output block arrays must specify an array size.
The vertex and fragment shader tests pass on Mesa. The
From: Ian Romanick ian.d.roman...@intel.com
THIS IS NOT REQUIRED BY ANY VERSION OF THE OpenGL SPECIFICATION!
However, almost every OpenGL implementation happens to behave this way
when there is a single vertex shader compilation unit linked into the
program. As a result, some programs
