diff options
author | Jason Ekstrand <[email protected]> | 2019-02-10 22:23:01 -0600 |
---|---|---|
committer | Jason Ekstrand <[email protected]> | 2019-02-11 10:57:23 -0600 |
commit | 9e6a6ef0d45a5bb61a541c495fe12e54e646ecfe (patch) | |
tree | c71a490da741ec44127b6210e954eb764ae08b25 /src/gallium/auxiliary/util/u_threaded_context.c | |
parent | fd77606b5b6365a15f2c7b7fcd97c35a67d4be57 (diff) |
nir/deref: Rematerialize parents in rematerialize_derefs_in_use_blocks
When nir_rematerialize_derefs_in_use_blocks_impl was first written, I
attempted to optimize things a bit by not bothering to re-materialize
the sources of deref instructions figuring that the final caller would
take care of that. However, in the case of more complex deref chains
where the first link or two lives in block A and then another link and
the load/store_deref intrinsic live in block B it doesn't work. The
code in rematerialize_deref_in_block looks at the tail of the chain,
sees that it's already in block B and skips it, not realizing that part
of the chain also lives in block A.
The easy solution here is to just rematerialize deref sources of deref
instructions as well. This may potentially lead to a few more deref
instructions being created by the conditions required for that to
actually happen are fairly unlikely and, thanks to the caching, it's all
linear time regardless.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109603
Fixes: 7d1d1208c2b "nir: Add a small pass to rematerialize derefs per-block"
Reviewed-by: Alejandro PiƱeiro <[email protected]>
Diffstat (limited to 'src/gallium/auxiliary/util/u_threaded_context.c')
0 files changed, 0 insertions, 0 deletions