tests: Do some housekeeping for Vulkan implementations nobody loves.
1 unresolved thread
1 unresolved thread
Merge request reports
Activity
Good point. I couldn't find any definitive answer, but from https://learn.microsoft.com/en-us/windows/win32/api/d3d12/ns-d3d12-d3d12_resource_uav_barrier it seems that barriers must always used between pairs of write operations (even if the second operation doesn't read, or at least doesn't apparently read; the page rather gives the negative version of this: you're allowed to skip the barrier between two read-only operations). I couldn't find any formal definition of what is a "write operation", so it's not clear whether a clear operation is a write operation. For the avoidance of doubt I'll pretend it is a fix the MR.
added 29 commits
-
f68d4200...4f0e5b90 - 24 commits from branch
wine:master
- f6fe9a39 - tests: Mark the HS punned array test as buggy on MoltenVK.
- cf816a25 - tests: Pop the test context when leaving its scope.
- 0c63824d - tests: Mark the coverage test as buggy on MoltenVK.
- 5e43f998 - tests: Relax precision a bit for an interpolation test.
- dff22c9e - tests: Clear the UAV before testing.
Toggle commit list-
f68d4200...4f0e5b90 - 24 commits from branch
Please register or sign in to reply