Summary: | [BDW Bisected]Ogles3conform ES3-CTS.shaders.uniform_block.random.nested_structs_arrays_instance_arrays.9 fails | ||
---|---|---|---|
Product: | Mesa | Reporter: | lu hua <huax.lu> |
Component: | Drivers/DRI/i965 | Assignee: | Matt Turner <mattst88> |
Status: | VERIFIED DUPLICATE | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | idr |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
lu hua
2015-02-02 03:07:05 UTC
Can you narrow the range at all? There are 194 commits between adc8cdf and 6094619. :( Run binary, it always pass, run this case via infrastructure, I can reproduce the fail. Bisected it. Bisect shows: c638ea3d19d46cfe65739af2c78373146ed50737 is the first bad commit commit c638ea3d19d46cfe65739af2c78373146ed50737 Author: Matt Turner <mattst88@gmail.com> AuthorDate: Wed Apr 9 13:38:14 2014 -0700 Commit: Matt Turner <mattst88@gmail.com> 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 (bug 78648). Tapani reapplied this patch and could not reproduce the bug with current Mesa. Reviewed-by: Kenneth Graunke <kenneth@whitecape.org> Reviewed-by: Jason Ekstrand <jason.ekstrand@intel.com> *** This bug has been marked as a duplicate of bug 88793 *** (In reply to lu hua from comment #2) > Run binary, it always pass, run this case via infrastructure, I can > reproduce the fail. Bisected it. For what it's worth, I tried reproducing this as well (since the failing testes in bug 88793 are full of spilling) and could not. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.