March 2024 - wine-gitlab

Re: [PATCH v2 0/1] MR712: tests: Use a UAV barrier between ClearUnorderedAccessViewFloat() and a compute shader. - approved
by Giovanni Mascellani (＠giomasce) 13 Mar '24

13 Mar '24

This merge request was approved by Giovanni Mascellani. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/712

1 0

[PATCH v3 0/7] MR5262: win32u: Refactor monitor cache to only store the necessary information.
by Rémi Bernon (＠rbernon) 13 Mar '24

13 Mar '24

-- v3: win32u: Enumerate monitors from their device keys. win32u: Get rid of the monitor flags. win32u: Get rid of the adapter display_device. win32u: Get rid of the monitor state_flags. win32u: Get rid of the monitor display_device. win32u: Split writing monitor to registry to a separate helper. win32u: Add an adapter struct to the device manager context. https://gitlab.winehq.org/wine/wine/-/merge_requests/5262

4 20

[PATCH v5 0/3] MR5060: win32u, explorer, winex11.drv: Restore display settings on process exit.
by Anton Baskanov (＠baskanov) 13 Mar '24

13 Mar '24

-- v5: win32u, explorer: Restore display settings on process exit. winex11.drv: Process RRNotify events in xrandr14_get_id. user32/tests: Test that display settings are restored on process exit. https://gitlab.winehq.org/wine/wine/-/merge_requests/5060

4 58

[PATCH v4 0/2] MR5220: win32u: Move vulkan d3dkmt implementation out of winex11.
by Rémi Bernon (＠rbernon) 13 Mar '24

13 Mar '24

-- v4: win32u: Move D3DKMT VidPn* functions out of winex11. win32u: Move D3DKMT functions to a new d3dkmt.c source. https://gitlab.winehq.org/wine/wine/-/merge_requests/5220

3 6

[PATCH 0/2] MR714: vkd3d-shader/dxil: Implement DX instruction BufferUpdateCounter.
by Conor McCarthy (＠cmccarthy) 13 Mar '24

13 Mar '24

-- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/714

2 2

[PATCH v6 0/13] MR707: vkd3d-shader/dxil: TGSM part 2.
by Conor McCarthy (＠cmccarthy) 13 Mar '24

13 Mar '24

Goes atop !681. The last 8 commits belong here. -- v6: vkd3d-shader/spirv: Emit a warning if atomic RMW flags are unhandled. vkd3d-shader/dxil: Implement the DXIL ATOMICRMW instruction. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/707

2 13

[PATCH v5 0/14] MR707: vkd3d-shader/dxil: TGSM part 2.
by Conor McCarthy (＠cmccarthy) 13 Mar '24

13 Mar '24

Goes atop !681. The last 8 commits belong here. -- v5: tests: Use DXIL code in test_tgsm(). https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/707

2 14

[PATCH v4 0/13] MR707: vkd3d-shader/dxil: TGSM part 2.
by Conor McCarthy (＠cmccarthy) 13 Mar '24

13 Mar '24

Goes atop !681. The last 8 commits belong here. -- v4: vkd3d-shader/spirv: Emit a warning if atomic RMW flags are unhandled. vkd3d-shader/dxil: Implement the DXIL ATOMICRMW instruction. vkd3d-shader/dxil: Implement DX instructions ThreadId, GroupId, ThreadIdInGroup and FlattenedThreadIdInGroup. tests/shader-runner: Add TGSM tests. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/707

2 13

[PATCH 0/1] MR712: tests: Use a UAV barrier between ClearUnorderedAccessViewFloat() and a compute shader.
by Zebediah Figura (＠zfigura) 13 Mar '24

13 Mar '24

-- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/712

2 1

Re: [PATCH v12 0/7] MR4449: winegstreamer: WMReader compressed output
by Yuxuan Shui (＠yshui) 12 Mar '24

12 Mar '24

On Tue Mar 12 14:10:01 2024 +0000, Alfred Agrell wrote: > Yes, that certainly would explain your symptoms, and why I never saw > those issues. That's why Proton has a beta period, isn't it? Sounds like > an easy fix, easier than comparing media types. > Code duplication certainly has drawbacks, but I don't think we can blame > me or WineHQ for this one; if you fork an active codebase, you get merge > conflicts, and sometimes even behavioral conflicts like this. We can't > let a fork constrain upstream development, can we? The safest way to > avoid such trouble is get your code upstreamed. > The stream order is indeed not guaranteed; as long as the input video > bytestream is the same, I'm trusting that the stream order is also the same. > Maybe that's naive of me, maybe it is indeed safe. I didn't check. I didn't mean to pass blame, so sorry if I came across as accusing. Information you provided helped me figure out the bug, so thanks again for that! And thank you for taking take to respond! -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4449#note_64497

1 0

2025

2024

2023

2022

wine-gitlab March 2024