March 2024 - wine-gitlab

[PATCH v2 0/4] MR5228: Administrator tokens, part 2: Create Wine processes with a limited token.
by Zebediah Figura (＠zfigura) 07 Mar '24

07 Mar '24

Second half of <https://gitlab.winehq.org/wine/wine/-/merge_requests/5118>. This uses a different approach, setting the process token from within the process after it is created. This avoids the need to always relay through start.exe. -- v2: server: Create processes using a limited administrator token by default. ntdll: Elevate processes if requested in the manifest. https://gitlab.winehq.org/wine/wine/-/merge_requests/5228

3 6

[PATCH v4 0/2] MR661: Draft: tests: Introduce custom test driver.
by Francisco Casas (＠fcasas) 07 Mar '24

07 Mar '24

Basically !427, but in the form of a custom test driver script. If I am not mistaken, for the driver script to run properly it is necessary to run "autoreconf" in the source directory and call the configure script again in the build directory. The output when running tests would be the same we currently have except for tests that don't PASS, in that case, detailed information for each failing line will appear. Make a failing test to try it! -- v4: tests: Get detailed information on failing tests. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/661

4 8

[PATCH 0/1] MR5260: mscoree: Implement CLRRuntimeHost_Start.
by Esme Povirk (＠madewokherd) 07 Mar '24

07 Mar '24

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

2 1

[PATCH v3 0/5] MR680: vkd3d-shader: Nearly get rid of vkd3d_shader_desc.
by Giovanni Mascellani (＠giomasce) 07 Mar '24

07 Mar '24

The only leftover field is SM1-specific, and I don't too much about how it's used, so I'm leaving it aside for now. It seems, however, that it could be moved directly to the parser (it seems to be only used for parsing and scanning). -- v3: vkd3d-shader: Remove the bytecode fields from vkd3d_shader_desc. vkd3d-shader/dxbc: Remove flag is_dxil. vkd3d-shader: Move shader signatures to vsir_program. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/680

3 9

[PATCH 0/1] MR5257: winex11: Set the correct visual even if alpha matches.
by Gabriel Ivăncescu (＠insn) 07 Mar '24

07 Mar '24

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

3 3

[PATCH v12 0/8] MR662: vkd3d-shader/ir: Introduce a better CFG structurizer, part 2.
by Giovanni Mascellani (＠giomasce) 07 Mar '24

07 Mar '24

~~This applies on top of !656, the last three commits belong here.~~ -- v12: vkd3d-shader/ir: Sort each loop by block label. vkd3d-shader/ir: Dump the loops in the control flow graph. vkd3d-shader/ir: Keep track of loops by header block. vkd3d-shader/ir: Keep a reference to the message context inside struct vsir_cfg. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/662

3 10

[PATCH v14 0/6] MR553: vkd3d-shader/d3d-asm: Dump the input and output signatures.
by Giovanni Mascellani (＠giomasce) 07 Mar '24

07 Mar '24

At some point I would like to have an assembler for TPF, so that it's easier to write and modify tests. This is a first step in that direction, fixing some kind of format for serializing signatures in the comment at the beginning of the assembler code. ~~I'm not decided yet on all details, so take this as an RFC for the moment.~~ -- v14: tests: Test emitting the signature. vkd3d-compiler: Add an option to emit the signature when disassembling. vkd3d-shader/d3d-asm: Support emitting the shader signature. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/553

3 9

[PATCH 0/9] MR683: vkd3d: Implement ID3D12Device8.
by Conor McCarthy (＠cmccarthy) 07 Mar '24

07 Mar '24

More commits in one MR than usual, but the implementations are quite short, and it's good to get them all in at once. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/683

3 10

Re: [PATCH v3 0/5] MR679: vkd3d-shader: Refactor common code between vkd3d_shader_compile() and vkd3d_shader_scan().
by Henri Verbeet (＠hverbeet) 07 Mar '24

07 Mar '24

> > I imagine this is to make vkd3d_shader_scan() more similar to vkd3d_shader_compile(), but I think vkd3d_unreachable() is worse than the existing code. > > Even if the source type is already validated by `vkd3d_shader_validate_compile_info()`? Which use do you see into validating the source type twice? It's more about disliking vkd3d_unreachable()/abort(). That's a discussion we've had a few times before, of course; what's different this time is that we've seen a number of bugs come in through WineHQ Bugzilla with assertions failing inside vkd3d-shader since the last time we had that discussion. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/679#note_63881

1 0

[PATCH v7 0/1] MR673: tests/shader-runner: Add sampler comparison tests.
by Conor McCarthy (＠cmccarthy) 07 Mar '24

07 Mar '24

-- v7: tests/shader-runner: Add sampler comparison tests. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/673

3 2

2025

2024

2023

2022

wine-gitlab March 2024