[Bug 105440] GEN7: rendering issue on citra
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Apr 4 05:23:00 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=105440
Jason Ekstrand <jason at jlekstrand.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Jason Ekstrand <jason at jlekstrand.net> ---
This is fixed with the following commit in master:
commit 800df942eadc5356840f5cbc2ceaa8a65c01ee91
Author: Jason Ekstrand <jason.ekstrand at intel.com>
Date: Fri Mar 23 11:05:04 2018 -0700
nir/lower_vec_to_movs: Only coalesce if the vec had a SSA destination
Otherwise we may end up trying to coalesce in a case such as
ssa_1 = fadd r1, r2
r3.x = fneg(r2);
r3 = vec4(ssa_1, ssa_1.y, ...)
and that would cause us to move the writes to r3 from the vec to the
fadd which would re-order them with respect to the write from the fneg.
In order to solve this, we just don't coalesce if the destination of the
vec is not SSA. We could try to get clever and still coalesce if there
are no writes to the destination of the vec between the vec and the ALU
source. However, since registers only come from phi webs and indirects,
the chances of having a vec with a register destination that is actually
coalescable into its source is very slim.
Shader-db results on Haswell:
total instructions in shared programs: 13657906 -> 13659101 (<.01%)
instructions in affected programs: 149291 -> 150486 (0.80%)
helped: 0
HURT: 592
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105440
Fixes: 2458ea95c56 "nir/lower_vec_to_movs: Coalesce movs on-the-fly when
possible"
Reported-by: Vadym Shovkoplias <vadym.shovkoplias at globallogic.com>
Tested-by: Vadym Shovkoplias <vadym.shovkoplias at globallogic.com>
Reviewed-by: Matt Turner <mattst88 at gmail.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180404/21472f71/attachment-0001.html>
More information about the intel-3d-bugs
mailing list