On Tue Apr 21 17:58:26 2026 +0000, Charlotte Pabst wrote:
I believe it was a performance vs. correctness tradeoff. To my understanding D3D12_FENCE_FLAG_SHARED is correct, but Paul told me that creating a fence with this flag would be quite expensive (and it is a bit of a niche use case), and so I dropped it - but with the freelist (which came later), fence creation would be cached. It probably doesn't make much sense to change it in this commit in hindsight, perhaps we could also squash the freelist commit and the additional test commit into the initial implementation. Yeah, irrespective of the `D3D12_FENCE_FLAG_SHARED`, it doesn't make a lot of sense to commit a certain implementation and then replace with another one immediately after.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/9777#note_137325