On Thu, Jun 11, 2015 at 8:27 AM, Jason Ekstrand wrote:
> On Thu, Jun 11, 2015 at 8:12 AM, Connor Abbott wrote:
>> The one thing this will hurt is that diff'ing shaders from before and
>> after an optimization becomes harder, since just printing the shader
>> will re-order the numbers and add spur
On Thu, Jun 11, 2015 at 8:12 AM, Connor Abbott wrote:
> The one thing this will hurt is that diff'ing shaders from before and
> after an optimization becomes harder, since just printing the shader
> will re-order the numbers and add spurious changes. If we want to make
> the result of doing INTEL_
The one thing this will hurt is that diff'ing shaders from before and
after an optimization becomes harder, since just printing the shader
will re-order the numbers and add spurious changes. If we want to make
the result of doing INTEL_DEBUG=fs more reasonable, we could just do
it at the end of the
Thanks Ken, this does make debugging NIR code a bit easier :)
Reviewed-by: Iago Toral Quiroga
On Wed, 2015-06-10 at 02:39 -0700, Kenneth Graunke wrote:
> This makes the SSA definitions use sequential numbers (0, 1, 2, ...)
> instead of seemingly random ones. There's not much point normally,
> b
This makes the SSA definitions use sequential numbers (0, 1, 2, ...)
instead of seemingly random ones. There's not much point normally,
but it makes debug output much easier to read.
Signed-off-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/brw_nir.c | 6 ++
1 file changed, 6 insertions(
