On 12/16/2015 10:59 AM, Iago Toral Quiroga wrote:
Some drivers can disable the FS unit if there is nothing in the shader code
that writes to an output (i.e. color, depth, etc). Right now, mesa has
a function to check for atomic buffers and the i965 driver also checks for
images. Refactor this
On Tue, 2015-12-22 at 10:39 +0200, Tapani Pälli wrote:
>
> On 12/16/2015 10:59 AM, Iago Toral Quiroga wrote:
> > Some drivers can disable the FS unit if there is nothing in the
> > shader code
> > that writes to an output (i.e. color, depth, etc). Right now, mesa
> > has
> > a function to check
Iago Toral writes:
> On Thu, 2015-12-17 at 16:29 +0200, Francisco Jerez wrote:
>> Iago Toral Quiroga writes:
>>
>> > Some drivers can disable the FS unit if there is nothing in the shader code
>> > that writes to an output (i.e. color, depth, etc). Right
Iago Toral Quiroga writes:
> Some drivers can disable the FS unit if there is nothing in the shader code
> that writes to an output (i.e. color, depth, etc). Right now, mesa has
> a function to check for atomic buffers and the i965 driver also checks for
> images. Refactor
On Thu, 2015-12-17 at 16:29 +0200, Francisco Jerez wrote:
> Iago Toral Quiroga writes:
>
> > Some drivers can disable the FS unit if there is nothing in the shader code
> > that writes to an output (i.e. color, depth, etc). Right now, mesa has
> > a function to check for
Some drivers can disable the FS unit if there is nothing in the shader code
that writes to an output (i.e. color, depth, etc). Right now, mesa has
a function to check for atomic buffers and the i965 driver also checks for
images. Refactor this logic into a generic function that we can use for
any