On 08/06/2013 01:34 PM, Matt Turner wrote:
On Tue, Aug 6, 2013 at 12:11 PM, Paul Berry wrote:
Based on what we've seen with AMD and nVidia so far, it seems like the
intended behaviour is probably: redeclarations of interface blocks are
prohibited, with the exception of gl_PerVertex (which may o
On 08/06/2013 12:11 PM, Paul Berry wrote:
[snip]
FYI, Ken and I just did some experiments on AMD's Catalyst driver, and
here's what we found:
For the record, this was with Catalyst 12.06 on a Radeon HD 3650. (I
haven't updated that machine in a while...)
[snip]
Based on what we've seen wit
On 6 August 2013 13:34, Matt Turner wrote:
> On Tue, Aug 6, 2013 at 12:11 PM, Paul Berry
> wrote:
> > Based on what we've seen with AMD and nVidia so far, it seems like the
> > intended behaviour is probably: redeclarations of interface blocks are
> > prohibited, with the exception of gl_PerVert
On Tue, Aug 6, 2013 at 12:11 PM, Paul Berry wrote:
> Based on what we've seen with AMD and nVidia so far, it seems like the
> intended behaviour is probably: redeclarations of interface blocks are
> prohibited, with the exception of gl_PerVertex (which may only be redeclared
> once in a given comp
On 6 August 2013 10:19, Ian Romanick wrote:
> On 08/02/2013 07:52 PM, Paul Berry wrote:
>
>> 1. Is it ok to declare an unsized array in an interface block? In other
>> words, is this ok?
>>
>> out blk {
>> vec4 foo[];
>> };
>>
>> The nVidia Linux driver allows this, but Mesa c
On 08/02/2013 07:52 PM, Paul Berry wrote:
1. Is it ok to declare an unsized array in an interface block? In other
words, is this ok?
out blk {
vec4 foo[];
};
The nVidia Linux driver allows this, but Mesa currently doesn't. AFAICT
the spec says it's ok. In fact, the spec de
1. Is it ok to declare an unsized array in an interface block? In other
words, is this ok?
out blk {
vec4 foo[];
};
The nVidia Linux driver allows this, but Mesa currently doesn't. AFAICT
the spec says it's ok. In fact, the spec defines the built-in interface
block gl_PerVertex
