[PATCH vkd3d 2/3] vkd3d-shader: Introduce a compile option to use Unknown format for typed UAV reads.

[Conor McCarthy]

On Thu, Jul 21, 2022 at 2:45 AM Henri Verbeet <hverbeet at gmail.com> wrote:

> So what this compile option then comes down to is using either the
> declared UAV type, or SpvImageFormatUnknown. And when not using
> SpvImageFormatUnknown, there's arguably still a bug of ignoring
> component counts. We could opt to not fix that bug, or fail shader
> compilation for those formats, but it doesn't seem terribly hard to
> fix, and I don't think there are that many additional formats anyway.
>

What do you propose to do for component counts? UAVs with < 4 components
are still declared in DXBC as vec4, and loads declare e.g. u1.xyzw as the
source. Information about the actual component count seems to be missing.
It is stored in DXIL, so maybe it can be used there, but not for SM < 6.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20220722/4cbf76d1/attachment.htm>