03d93abc1a
There is a risk that we try to preserve a loop variable through multiple iterations, even though the dominating block is inside a loop. Fix this by analyzing if a block starts off by writing to a variable. In that case, there cannot be any preservation going on. If we don't, pretend the loop header is reading the variable, which moves the variable to an appropriate scope. |
||
---|---|---|
.. | ||
execute_callable.nocompat.vk.rgen.vk | ||
pure_call.nocompat.vk.rgen.vk | ||
ray_tracing.nocompat.vk.rgen.vk | ||
shader_record_buffer.nocompat.vk.rgen.vk |