I think this has two issues:
1) We don't properly handles stores, which should be disabled.
2) this could turn a loop which only has a discard as exit into an
infinite loop.
Also have we confirmed that LLVM 6.0+ works correctly?
On Thu, May 10, 2018 at 11:43 AM, Samuel Pitoiset
wrote:
> D3D be
D3D behaviour and Vulkan are different. The workaround can
be enabled with RADV_DEBUG=correctderivsafterkill.
When enabled, this fixes rendering issues with DXVK. For
now, I don't want to force-enable this behaviour for DXVK
because having per-app workarounds is a bad idea.
We are probably going
