Re: [PATCH 0/2] MR345: vkd3d-shader/dxil: Fix a couple of issues.

[Giovanni Mascellani (＠giomasce)]

Giovanni Mascellani (@giomasce) commented about libs/vkd3d-shader/dxil.c:
>  sm6_parser_init_output_signature(sm6, output_signature);
>
> - if (version.type == VKD3D_SHADER_TYPE_COMPUTE)
> -
>    sm6_parser_emit_thread_group(sm6);

I'm not sure I understand what's to be gained here: this look like a workaround for a specific crash of a Vulkan implementation, but SM6 support is still so early that there is basically no compute shader that you can throw at it. So why should we address this specific crash?