Timothy Arceri writes:
> On 03/07/18 05:51, Eric Anholt wrote:
>
>> Eric Anholt writes:
>>
>>> [ Unknown signature status ]
>>> Timothy Arceri writes:
>>>
nir_compact_varyings() is meant to skip over varyings used by xfb:
/* We can't repack xfb varyings. */
On 03/07/18 05:51, Eric Anholt wrote:
Eric Anholt writes:
[ Unknown signature status ]
Timothy Arceri writes:
nir_compact_varyings() is meant to skip over varyings used by xfb:
/* We can't repack xfb varyings. */
if (var->data.always_active_io)
continue
Eric Anholt writes:
> [ Unknown signature status ]
> Timothy Arceri writes:
>
>> nir_compact_varyings() is meant to skip over varyings used by xfb:
>>
>> /* We can't repack xfb varyings. */
>> if (var->data.always_active_io)
>> continue;
>>
>> Any idea why that i
Timothy Arceri writes:
> nir_compact_varyings() is meant to skip over varyings used by xfb:
>
> /* We can't repack xfb varyings. */
> if (var->data.always_active_io)
> continue;
>
> Any idea why that isn't working in this case?
Looks like GLSL IR has that flag wr
nir_compact_varyings() is meant to skip over varyings used by xfb:
/* We can't repack xfb varyings. */
if (var->data.always_active_io)
continue;
Any idea why that isn't working in this case?
On 21/06/18 06:30, Eric Anholt wrote:
If one of the TF variables got vary
If one of the TF variables got varying-packed, it would end up with a new
driver_location, despite the pipe_stream_output already being set up for
the old driver location. This left the gallium driver with no way to work
back to what varying was referenced by pipe_stream_output.
Fixes these tests
