mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-01 08:08:06 +02:00
nir/opt_dead_cf: Clarify comment
Make it obvious that the comment is about the block stitching behavior of nir_cf_node_remove. Reviewed-by: Rhys Perry <pendingchaos02@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/22064>
This commit is contained in:
parent
4b5737b785
commit
f160f7c525
1 changed files with 5 additions and 4 deletions
|
|
@ -312,10 +312,11 @@ dead_cf_list(struct exec_list *list, bool *list_ends_in_jump)
|
|||
case nir_cf_node_block: {
|
||||
nir_block *block = nir_cf_node_as_block(cur);
|
||||
while (dead_cf_block(block)) {
|
||||
/* We just deleted the if or loop after this block, so we may have
|
||||
* deleted the block before or after it -- which one is an
|
||||
* implementation detail. Therefore, to recover the place we were
|
||||
* at, we have to use the previous cf_node.
|
||||
/* We just deleted the if or loop after this block.
|
||||
* nir_cf_node_remove may have deleted the block before
|
||||
* or after it -- which one is an implementation detail.
|
||||
* Therefore, to recover the place we were at, we have
|
||||
* to use the previous cf_node.
|
||||
*/
|
||||
|
||||
if (prev) {
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue