September 2023 - Wine-GitLab

[PATCH v28 0/1] MR3074: Move getpeername() implementation to wineserver
by Ally Sommers (＠dropbear) Sept. 19, 2023

Sept. 19, 2023

`getpeername()` is currently handled in ntdll. This merge request changes ntdll to forward `getpeername()` to wineserver. The implementation utilises new `peer_addr` and `peer_addr_len` fields in wineserver's `struct sock`. This fixes multiple `todo_wine`s in `ws2_32/tests` and allows for more accurate peer names to be provided in case the address the socket is bound to on the Unix side does not match what `bind()` was called with on the Windows side. *This merge request was originally intended to be included in !2786 (Add support for AF_UNIX sockets) but was split into its own merge request because this is not an insignificant change.* -- v28: server: Move getpeername() implementation from ntdll/unix. https://gitlab.winehq.org/wine/wine/-/merge_requests/3074

3 2

Re: [PATCH v8 0/3] MR3855: Fixes for ntlea
by Yuxuan Shui (＠yshui) Sept. 19, 2023

Sept. 19, 2023

update: rebasing -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3855#note_45876

1 0

[PATCH 0/1] MR349: vkd3d-shader/spirv: Ensure that all instructions belong to a block.
by Giovanni Mascellani (＠giomasce) Sept. 19, 2023

Sept. 19, 2023

This is done by creating dummy blocks, which do not have any incoming branch. SPIR-V specification doesn't allow instructions not belonging to any block. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/349

5 9

[PATCH v3 0/1] MR3791: widl: Add initial implementation of the SLTG typelib generator.
by Dmitry Timoshkov (＠dmitry) Sept. 19, 2023

Sept. 19, 2023

-- v3: widl: Add initial implementation of SLTG typelib generator. https://gitlab.winehq.org/wine/wine/-/merge_requests/3791

2 1

[PATCH 0/5] MR3884: winegstreamer/aac decoder: Correctly handle various number of channels in transform_GetOutputAvailableType().
by Paul Gofman (＠gofman) Sept. 19, 2023

Sept. 19, 2023

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/3884

4 10

[PATCH v2 0/1] MR3791: widl: Add initial implementation of the SLTG typelib generator.
by Dmitry Timoshkov (＠dmitry) Sept. 19, 2023

Sept. 19, 2023

-- v2: widl: Add initial implementation of SLTG typelib generator. https://gitlab.winehq.org/wine/wine/-/merge_requests/3791

3 11

[PATCH 0/1] MR3888: ntdll: Allow empty application nodes in actctx.
by eric pouech (＠epo) Sept. 19, 2023

Sept. 19, 2023

Signed-off-by: Eric Pouech <epouech(a)codeweavers.com> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3888

3 4

[PATCH 0/1] MR3889: include: Update the d3d12 headers from vkd3d.
by Martin Storsjö Sept. 19, 2023

Sept. 19, 2023

This corresponds to vkd3d as of commit e597b0d80f39f716a8740cb0be55edc78f4599d6. This brings in a function signature fix for the implementation of ID3D12CommandQueue::UpdateTileMappings() as well, from vkd3d commit e98e6c9b530995e68bd019a3319d90223ed864cf. Signed-off-by: Martin Storsjö <martin(a)martin.st> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3889

1 1

Re: [PATCH v7 0/2] MR328: ci: Run the tests on macOS.
by Giovanni Mascellani (＠giomasce) Sept. 19, 2023

Sept. 19, 2023

On Tue Sep 19 08:41:58 2023 +0000, Chip Davis wrote: > Can you set this up to let me and possibly Bill Hollings know if CI on > Mac breaks and it's not your fault? I'd really appreciate knowing when > we've broken things for you. I don't think this is the most appropriate place to detect MoltenVK regressions, because we don't use MoltenVK from git, but a released version, which I think is installed through brew. I don't even think it is the latest released version. At any rate, even when there is a regression I don't have an automated way to know whether what's broken is vkd3d or MoltenVK. Also, notice that currently vkd3d is broken in many ways on top of MoltenVK (the CI job is marked as allowed to fail for this reason); test `d3d12` even segfaults (I am preparing some patches for that). Before this can give a useful signal vkd3d tests should be appropriately marked as todo on MoltenVK, so that actual breakages can be detected. Eventually I hope to do that, but it might take a while (for example, I've been planning to do the same for Intel and NVIDIA on Linux, which have similarly been broken for a long time if not forever; and it hasn't happened yet). Of course we'll be happy to take patches, if you have so me bandwidth for that. To address my first concern, I'd suggest to avoid using this specific project, but rather set up another one that tracks both vkd3d and MoltenVK development branches, and run the tests each time any of the two projects is committed to: this might help to give an idea of which project broke it when there is a problem. Or maybe run the stable vkd3d on the development MoltenVK, I don't know. I can help to set this up, but marking the tests as todo must be done before. BTW, the macOS runner available here is based on an Intel chip. In your experience, can testing on Intel be considered representative of the M1 behavior too, or should we come up with an M1 runner too? -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/328#note_45856

1 0

[PATCH 0/1] MR3885: include: Move RTL functions that belong in winnt.h from winternl.h to winnt.h.
by Alex Henrie (＠alexhenrie) Sept. 19, 2023

Sept. 19, 2023

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/3885

2 1