Atomic ops on images with Unknown type will cause SPIR-V validation failure,
and assertion failure in Mesa debug builds. D3D12 allows atomics on typed
buffers, and this requires a distinction to be made between UAV reads and
atomic ops.
--
v2: vkd3d-shader: Introduce DESCRIPTOR_INFO_FLAG_UAV_ATOMICS and always declare UAV images with known type for atomic ops.
tests: Test a typed UAV buffer in test_atomic_instructions().
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/49
This is my first time implementing an interface so thorough feedback would be appreciated.
--
v7: windows.media: Implement IClosedCaptionPropertiesStatics interface.
windows.media: Add stub DLL.
include/windowscontracts: Bump contractversion to 14.
https://gitlab.winehq.org/wine/wine/-/merge_requests/1343
This avoids the following warning by GCC 13:
dlls/msado15/recordset.c:790:32: warning: 'i' may be used uninitialized
--
v2: msado15: Avoid uninitialized variable use in fields_get_Item
https://gitlab.winehq.org/wine/wine/-/merge_requests/1449