On Wed, 2016-01-06 at 17:50 -0500, Ilia Mirkin wrote:
> On Tue, Dec 29, 2015 at 12:00 AM, Timothy Arceri
> wrote:
> > Tessellation shaders treat varyings as shared memory and
> > invocations
> > can access each others varyings therefore we can't use the existing
> >
On Tue, 2015-12-29 at 17:38 +1100, eocallag...@alterapraxis.com wrote:
> On 2015-12-29 16:00, Timothy Arceri wrote:
> > Tessellation shaders treat varyings as shared memory and
> > invocations
> > can access each others varyings therefore we can't use the existing
> > method to lower them.
> >
>
On Wed, Jan 6, 2016 at 6:40 PM, Timothy Arceri
wrote:
> On Wed, 2016-01-06 at 17:50 -0500, Ilia Mirkin wrote:
>> On Tue, Dec 29, 2015 at 12:00 AM, Timothy Arceri
>> wrote:
>> > Tessellation shaders treat varyings as shared memory and
>>
On Tue, Dec 29, 2015 at 12:00 AM, Timothy Arceri
wrote:
> Tessellation shaders treat varyings as shared memory and invocations
> can access each others varyings therefore we can't use the existing
> method to lower them.
That's not strictly true... this is only true
On Wed, 2016-01-06 at 18:45 -0500, Ilia Mirkin wrote:
> On Wed, Jan 6, 2016 at 6:40 PM, Timothy Arceri
> wrote:
> > On Wed, 2016-01-06 at 17:50 -0500, Ilia Mirkin wrote:
> > > On Tue, Dec 29, 2015 at 12:00 AM, Timothy Arceri
> > >
Tessellation shaders treat varyings as shared memory and invocations
can access each others varyings therefore we can't use the existing
method to lower them.
This adds a check for these stages as following patches will
allow explicit locations to be lowered even when the driver and existing
On 2015-12-29 16:00, Timothy Arceri wrote:
Tessellation shaders treat varyings as shared memory and invocations
can access each others varyings therefore we can't use the existing
method to lower them.
This adds a check for these stages as following patches will
allow explicit locations to be