September 2023 - Wine-gitlab

[PATCH 0/10] MR3796: mshtml: Implement a unified QueryInterface on the dispex, part 4.
by Gabriel Ivăncescu 12 Sep '23

12 Sep '23

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

2 16

[PATCH v3 0/1] MR336: vkd3d-shader/hlsl: Fix float modulus for vector arguments.
by Nikolay Sivov (＠nsivov) 12 Sep '23

12 Sep '23

Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> -- v3: vkd3d-shader/hlsl: Fix float modulus for vector arguments. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/336

4 6

[PATCH v7 0/13] MR317: vkd3d-shader: Begin validating the generated IR.
by Giovanni Mascellani (＠giomasce) 12 Sep '23

12 Sep '23

The validation code is meant both as a check that the frontend is behaving properly and as a sort of the documentation to establish what is allowed and what is not in the IR. ~~Currently an assertion is thrown if validation fails. I realize this is a rather strong proposal, but it's of course up for debate. In theory asserting here is the right thing, as it is expected that the frontend is generating correct IR code. However vkd3d is already used in production for many programs, and it could very well be that some of those are working properly even if the generated IR is somewhat out of specs; allowing the assertion might cause regressions as soon as enough checks are implemented in the validator. Please let me know your opinions.~~ **Solved in favor of a softer failure, and only when validation is enabled** -- v7: vkd3d-shader/ir: Validate source parameters. vkd3d-shader/ir: Validate destination parameters. vkd3d-shader/ir: Validate register types. vkd3d-shader/ir: Validate instruction handlers. vkd3d-shader/ir: Introduce a boilerplate to validate the generated IR. vkd3d-shader: Embed the parsing location in vkd3d_shader_instruction. vkd3d-shader/dxil: Destroy the SM6 parser on parsing errors. vkd3d-shader/tpf: Destroy the SM4 parser on parsing errors. vkd3d-shader/d3dbc: Destroy the SM1 parser on parsing errors. vkd3d-shader/d3dbc: Ignore DCL source parameters. vkd3d-shader/ir: Simplify the control flow in shader_instruction_normalise_io_params(). vkd3d-shader/ir: Fully reinitialize an instruction when making it a NOP. vkd3d-shader: Rename shader_instruction_init(). https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/317

4 15

[PATCH v4 0/1] MR3767: msvcp110: Add std::_Throw_future_error.
by Daniel Lehman (＠dlehman25) 12 Sep '23

12 Sep '23

-- v4: msvcp110: Add std::_Throw_future_error. https://gitlab.winehq.org/wine/wine/-/merge_requests/3767

3 4

[PATCH v3 0/1] MR3752: d2d1: Respect stroke style D2D1_STROKE_TRANSFORM_TYPE_FIXED in DrawGeometry::ID2D1DeviceContext1().
by Dmitry Timoshkov (＠dmitry) 12 Sep '23

12 Sep '23

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54368 -- v3: d2d1: Scale stroke width for D2D1_STROKE_TRANSFORM_TYPE_FIXED in DrawGeometry::ID2D1DeviceContext1(). https://gitlab.winehq.org/wine/wine/-/merge_requests/3752

3 2

[PATCH v5 0/2] MR328: ci: Run the tests on macOS.
by Giovanni Mascellani (＠giomasce) 12 Sep '23

12 Sep '23

-- v5: ci: Do not drop artifacts after 1 day. ci: Run the tests on macOS. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/328

2 2

[PATCH v2 0/1] MR3752: d2d1: Respect stroke style D2D1_STROKE_TRANSFORM_TYPE_FIXED in DrawGeometry::ID2D1DeviceContext1().
by Dmitry Timoshkov (＠dmitry) 12 Sep '23

12 Sep '23

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54368 -- v2: d2d1: Respect stroke style D2D1_STROKE_TRANSFORM_TYPE_FIXED in DrawGeometry::ID2D1DeviceContext1(). https://gitlab.winehq.org/wine/wine/-/merge_requests/3752

4 6

[PATCH v2 0/1] MR3736: winmm: Use CRT allocation functions.
by Alex Henrie (＠alexhenrie) 12 Sep '23

12 Sep '23

-- v2: winmm: Use CRT allocation functions. https://gitlab.winehq.org/wine/wine/-/merge_requests/3736

3 3

Re: [PATCH v4 0/5] MR3792: Fill in some VMR9 stubs
by Alfred Agrell (＠Alcaro) 12 Sep '23

12 Sep '23

Oops, forgot updating that 'out of memory' string. Fixed. Also rebased. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3792#note_44985

1 0

[PATCH 0/1] MR3793: regedit: Export hex(4) instead of dword if size isn't 4 bytes.
by Ryan Hendrickson (＠rhendric) 12 Sep '23

12 Sep '23

If a Windows program writes a registry key of type REG_DWORD but puts more than 4 bytes of data in—I can't imagine why, but I am working with such a program—currently it is persisted as-is in the `WINEPATH` but `regedit` exports it as a `dword:%08x`, truncating the data. This patch makes sure that only 4-byte DWORDs are exported as `dword:`; any other size falls through as a `hex(4):`. (I chose to use the literal `4` here instead of `sizeof(DWORD)` because this value isn't directly coupled to the size of a `DWORD` as the compiler sees it; in the (extremely hypothetical?) world in which Wine is compiled with a `DWORD` of some other size, this value should still be 4, because `export_dword_data` will only correctly export something that can be represented in 8 hexadecimal characters.) -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3793

2 1