On Fri, May 13, 2016 at 9:13 PM, Connor Abbott wrote:
> On Fri, May 13, 2016 at 9:07 PM, Rob Clark wrote:
>> On Fri, May 13, 2016 at 8:23 PM, Connor Abbott wrote:
>>> On Fri, May 13, 2016 at 4:14 PM, Rob Clark wrote:
On Fri, May 13, 2016 at 4:10 PM, Jason Ekstrand
wrote:
> On Fr
On Fri, May 13, 2016 at 9:07 PM, Rob Clark wrote:
> On Fri, May 13, 2016 at 8:23 PM, Connor Abbott wrote:
>> On Fri, May 13, 2016 at 4:14 PM, Rob Clark wrote:
>>> On Fri, May 13, 2016 at 4:10 PM, Jason Ekstrand
>>> wrote:
On Fri, May 13, 2016 at 1:02 PM, Rob Clark wrote:
>
> From
On Fri, May 13, 2016 at 8:23 PM, Connor Abbott wrote:
> On Fri, May 13, 2016 at 4:14 PM, Rob Clark wrote:
>> On Fri, May 13, 2016 at 4:10 PM, Jason Ekstrand wrote:
>>> On Fri, May 13, 2016 at 1:02 PM, Rob Clark wrote:
From: Rob Clark
If we assert in nir_validate_shader(), p
On Fri, May 13, 2016 at 4:14 PM, Rob Clark wrote:
> On Fri, May 13, 2016 at 4:10 PM, Jason Ekstrand wrote:
>> On Fri, May 13, 2016 at 1:02 PM, Rob Clark wrote:
>>>
>>> From: Rob Clark
>>>
>>> If we assert in nir_validate_shader(), print the shader with the
>>> offending instruction prefixed wit
Rob Clark writes:
> From: Rob Clark
>
> If we assert in nir_validate_shader(), print the shader with the
> offending instruction prefixed with "=>" to make it easier to find what
> part of the shader nir_validate is complaining about.
>
> Macro funny-business in nir_validate() was just to avoid
On Fri, May 13, 2016 at 4:14 PM, Rob Clark wrote:
> On Fri, May 13, 2016 at 4:10 PM, Jason Ekstrand wrote:
>> On Fri, May 13, 2016 at 1:02 PM, Rob Clark wrote:
>>>
>>> From: Rob Clark
>>>
>>> If we assert in nir_validate_shader(), print the shader with the
>>> offending instruction prefixed wit
On Fri, May 13, 2016 at 4:10 PM, Jason Ekstrand wrote:
> On Fri, May 13, 2016 at 1:02 PM, Rob Clark wrote:
>>
>> From: Rob Clark
>>
>> If we assert in nir_validate_shader(), print the shader with the
>> offending instruction prefixed with "=>" to make it easier to find what
>> part of the shader
On Fri, May 13, 2016 at 1:02 PM, Rob Clark wrote:
> From: Rob Clark
>
> If we assert in nir_validate_shader(), print the shader with the
> offending instruction prefixed with "=>" to make it easier to find what
> part of the shader nir_validate is complaining about.
>
> Macro funny-business in n
From: Rob Clark
If we assert in nir_validate_shader(), print the shader with the
offending instruction prefixed with "=>" to make it easier to find what
part of the shader nir_validate is complaining about.
Macro funny-business in nir_validate() was just to avoid changing a
bazillion assert() li
