<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BDW Bisected]Piglit/shaders_glsl-max-varyings fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88793">88793</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[BDW Bisected]Piglit/shaders_glsl-max-varyings fails
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>high
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/DRI/i965
</td>
</tr>
<tr>
<th>Assignee</th>
<td>mattst88@gmail.com
</td>
</tr>
<tr>
<th>Reporter</th>
<td>huax.lu@intel.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>idr@freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>System Environment:
--------------------------
Platform: BDW
Libdrm:
(master)libdrm-2.4.59-2-g0c5aaeef51233aec89ee1f43f03d457f278f8fa0
Mesa: (master)0aa31bf9c37e11c041f951342f38c38907c620ff
Xserver: (master)xorg-server-1.16.99.902
Xf86_video_intel:
(master)2.99.917-50-ged19b160089640c2e1167332b00ffe1e569a48dc
Libva: (master)f9741725839ea144e9a6a1827f74503ee39946c3
Libva_intel_driver: (master)3d16cf07b6b65b9bd5c2dd855d97558264a12e79
Kernel: (drm-intel-nightly)67e9eb08a3b967b1ac6b7ec4588a93a2cb030cae
Bug detailed description:
---------------------------
It fails on BDW with mesa master branch, works well on 10.4 branch.
Following cases also fail with the same bisect commit.
Piglit/shaders_glsl-max-varyings_>MAX_VARYING_COMPONENTS
Piglit/spec_glsl-1.10_execution_varying-packing_simple_int_array
Piglit/spec_glsl-1.10_execution_varying-packing_simple_int_separate
Piglit/spec_glsl-1.10_execution_varying-packing_simple_ivec2_array
Piglit/spec_glsl-1.10_execution_varying-packing_simple_ivec2_separate
Piglit/spec_glsl-1.10_execution_varying-packing_simple_ivec4_array
Piglit/spec_glsl-1.10_execution_varying-packing_simple_ivec4_separate
Piglit/spec_glsl-1.10_execution_varying-packing_simple_uint_array
Piglit/spec_glsl-1.10_execution_varying-packing_simple_uint_separate
Piglit/spec_glsl-1.10_execution_varying-packing_simple_uvec2_array
Piglit/spec_glsl-1.10_execution_varying-packing_simple_uvec2_separate
Piglit/spec_glsl-1.10_execution_varying-packing_simple_uvec4_array
Piglit/spec_glsl-1.10_execution_varying-packing_simple_uvec4_separate
Piglit/spec_glsl-1.30_execution_varying-packing-mixed-types
Bisect shows: c638ea3d19d46cfe65739af2c78373146ed50737 is the first bad commit
commit c638ea3d19d46cfe65739af2c78373146ed50737
Author: Matt Turner <<a href="mailto:mattst88@gmail.com">mattst88@gmail.com</a>>
AuthorDate: Wed Apr 9 13:38:14 2014 -0700
Commit: Matt Turner <<a href="mailto:mattst88@gmail.com">mattst88@gmail.com</a>>
CommitDate: Fri Jan 23 17:57:39 2015 -0800
i965: Don't make instructions with a null dest a barrier to scheduling.
Now that we properly track accumulator dependencies, the scheduler is
able to schedule instructions between the mach and mov in the common
the integer multiplication pattern:
mul acc0, x, y
mach null, x, y
mov dest, acc0
Since a null destination implies no dependency on the destination, we
can also safely schedule instructions (that don't write the accumulator)
between the mul and mach.
GAINED: 103
LOST: 43
Causes one program to spill (643 -> 1076 instructions).
I committed this patch last year (commit 42a26cb5) but reverted it
(commit 0d3f83f4) after inexplicable artifacts in Kerbal Space Program
(<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Texture artifacts in Kerbal Space Program"
href="show_bug.cgi?id=78648">bug 78648</a>). Tapani reapplied this patch and could not reproduce the bug
with current Mesa.
Reviewed-by: Kenneth Graunke <<a href="mailto:kenneth@whitecape.org">kenneth@whitecape.org</a>>
Reviewed-by: Jason Ekstrand <<a href="mailto:jason.ekstrand@intel.com">jason.ekstrand@intel.com</a>>
output:
libGL: OpenDriver: trying /opt/X11R7/lib/dri/tls/i965_dri.so
libGL: OpenDriver: trying /opt/X11R7/lib/dri/i965_dri.so
Vertical axis: Increasing numbers of varyings.
Horizontal axis: Which of the varyings contains the color.
GL_MAX_VARYING_FLOATS = 128
Probe color at (90,94)
Expected: 0.000000 1.000000 0.000000
Observed: 0.501961 0.501961 0.501961
Failure with 24 vec4 varyings used in varying index 22
Probe color at (90,98)
Expected: 0.000000 1.000000 0.000000
Observed: 0.501961 0.501961 0.501961
Failure with 25 vec4 varyings used in varying index 22
Probe color at (2,102)
Expected: 0.000000 1.000000 0.000000
Observed: 0.000000 0.000000 0.000000
Failure with 26 vec4 varyings used in varying index 0
Probe color at (6,106)
Expected: 0.000000 1.000000 0.000000
Observed: 0.000000 0.000000 0.000000
Failure with 27 vec4 varyings used in varying index 1
Probe color at (2,110)
Expected: 0.000000 1.000000 0.000000
Observed: 1.000000 1.000000 0.000000
Failure with 28 vec4 varyings used in varying index 0
Probe color at (6,114)
Expected: 0.000000 1.000000 0.000000
Observed: 0.000000 0.000000 0.000000
Failure with 29 vec4 varyings used in varying index 1
Probe color at (2,118)
Expected: 0.000000 1.000000 0.000000
Observed: 0.501961 0.501961 0.501961
Failure with 30 vec4 varyings used in varying index 0
Probe color at (6,122)
Expected: 0.000000 1.000000 0.000000
Observed: 0.000000 0.000000 0.000000
Failure with 31 vec4 varyings used in varying index 1
Probe color at (2,126)
Expected: 0.000000 1.000000 0.000000
Observed: 1.000000 0.000000 0.000000
Failure with 32 vec4 varyings used in varying index 0
PIGLIT: {"result": "fail" }
Reproduce steps:
-------------------------
1. xinit
2. ./bin/glsl-max-varyings -auto -fbo</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>