Do we (still) need this? I think tracing DXIL should largely work now.
It prints the reason for failure where we'd have only the generic error -3, but this will disappear soon so we don't really need it.
Do we need this? And perhaps more importantly, if we do need this, do we need this right away? For the purpose of vkd3d-compiler and vkd3d, we can just use vkd3d_shader_parse_dxbc() now, without making this part of the public API.
I don't see how to get this info from `vkd3d_shader_parse_dxbc()` without parsing the returned chunk tags, which would belong in vkd3d-shader anyway. It's very convenient to just use `compile_info.source_type = VKD3D_SHADER_SOURCE_DXBC_AUTODETECT` in state.c.
Along a similar vein, does this add much over the existing autodetection we have in vkd3d-compiler?
It avoids failure of `get_source_type_info()` for `VKD3D_SHADER_SOURCE_DXBC_AUTODETECT`. It could be worked around but this is a simple fix.
In the current split it takes 17 patches just to reach the point where a pixel shader with const output will compile, and there are far more to come. Unless we know of a specific problem caused by adding autodetect to the public API I would rather continue toward SM 6 compilation being largely complete. Until we have that, issues like the granularity of specific warnings/errors emitted with vkd3d_shader_error() must also have low priority.