diff options
author | Jason Ekstrand <[email protected]> | 2018-03-23 11:05:04 -0700 |
---|---|---|
committer | Jason Ekstrand <[email protected]> | 2018-04-03 22:21:23 -0700 |
commit | 800df942eadc5356840f5cbc2ceaa8a65c01ee91 (patch) | |
tree | ca569064b62ece5cb22f2df107d7a02b2f2f4db1 /src/mesa/drivers | |
parent | 5bbde9b80fe2e6a384db5d636725b8f8065bc5c5 (diff) |
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 <[email protected]>
Tested-by: Vadym Shovkoplias <[email protected]>
Reviewed-by: Matt Turner <[email protected]>
Diffstat (limited to 'src/mesa/drivers')
0 files changed, 0 insertions, 0 deletions