Re: [Mesa-dev] [PATCH 1/2] glsl: allow inputs in interface blocks in interpolateAt*

2017-06-19 Thread Ian Romanick
On 06/19/2017 04:45 AM, Nicolai Hähnle wrote: > On 18.06.2017 21:18, Ian Romanick wrote: >> On 06/16/2017 01:37 PM, Nicolai Hähnle wrote: >>> From: Nicolai Hähnle >>> >>> Since interface blocks are simply considered groupings of input >>> variables, >>> this is allowed. >>> >>> var->data.must_be_s

Re: [Mesa-dev] [PATCH 1/2] glsl: allow inputs in interface blocks in interpolateAt*

2017-06-19 Thread Nicolai Hähnle
On 18.06.2017 21:18, Ian Romanick wrote: On 06/16/2017 01:37 PM, Nicolai Hähnle wrote: From: Nicolai Hähnle Since interface blocks are simply considered groupings of input variables, this is allowed. var->data.must_be_shader_input is now determined on-the-fly after lowering interface blocks,

Re: [Mesa-dev] [PATCH 1/2] glsl: allow inputs in interface blocks in interpolateAt*

2017-06-18 Thread Ian Romanick
On 06/16/2017 01:37 PM, Nicolai Hähnle wrote: > From: Nicolai Hähnle > > Since interface blocks are simply considered groupings of input variables, > this is allowed. > > var->data.must_be_shader_input is now determined on-the-fly after lowering > interface blocks, since we don't want to disable

[Mesa-dev] [PATCH 1/2] glsl: allow inputs in interface blocks in interpolateAt*

2017-06-16 Thread Nicolai Hähnle
From: Nicolai Hähnle Since interface blocks are simply considered groupings of input variables, this is allowed. var->data.must_be_shader_input is now determined on-the-fly after lowering interface blocks, since we don't want to disable varying packing for an entire block just because one input