- wine-gitlab - winehq.org

[PATCH 0/1] MR1933: wininet/tests: Pass INTERNET_FLAG_RELOAD in secure connection tests.
by Hans Leidekker (＠hans) 11 Jan '23

11 Jan '23

Avoids test failures when the URL is cached by other tests. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51227 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1933

3 2

[PATCH v2 0/2] MR1931: ntdll: Conform to Windows 11 behavior in RtlIpv6StringToAddress().
by Hans Leidekker (＠hans) 11 Jan '23

11 Jan '23

Also fixes test failures on Windows 11. Wine-Bug: https://bugs.winehq.org//show_bug.cgi?id=54045 -- v2: ntdll: Conform to Windows 11 behavior in RtlIpv6StringToAddress(). ws2_32/tests: Fix test failures on Windows 11. https://gitlab.winehq.org/wine/wine/-/merge_requests/1931

3 4

[PATCH v6 0/5] MR54: vkd3d-shader/hlsl: Initialize static variables to 0 by default.
by Francisco Casas (＠fcasas) 11 Jan '23

11 Jan '23

We are currently not initializing static values to zero by default. Consider the following shader: ```hlsl static float4 va; float4 main() : sv_target { return va; } ``` we get the following output: ``` ps_5_0 dcl_output o0.xyzw dcl_temps 2 mov r0.xyzw, r1.xyzw mov o0.xyzw, r0.xyzw ret ``` where r1.xyzw is not initialized. This patch solves this by assigning the static variable the value of an uint 0, and thus, relying on complex broadcasts. This seems to be the behaviour of the the native compiler, since it retrieves the following error on a shader that lacks an initializer on a data type with object components: ``` error X3017: cannot convert from 'uint' to 'struct <unnamed>' ``` -- v6: vkd3d-shader/hlsl: Allow uninitialized static objects. vkd3d-shader/hlsl: Validate that non-uniform objects are not referenced. tests: Add additional object references tests. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/54

6 14

[PATCH v3 0/5] MR47: hlsl: Function calls.
by Zebediah Figura (＠zfigura) 11 Jan '23

11 Jan '23

-- v3: vkd3d-shader/hlsl: Get rid of the "intrinsic" field of struct hlsl_ir_function. vkd3d-shader/hlsl: Forbid returning void expressions from void functions. vkd3d-shader/hlsl: Generate IR for user-defined function calls. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/47

3 6

[PATCH 0/1] MR57: tests: Print d3dcompiler_47.dll version when running tests on Windows.
by Giovanni Mascellani (＠giomasce) 11 Jan '23

11 Jan '23

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

4 4

Re: [PATCH v2 0/4] MR1899: kernel32/tests: Call newer functions not on Windows XP or 2003 via function addresses (process)
by Hugh McMaster (＠hmc) 11 Jan '23

11 Jan '23

For the console tests, I prefer to run new/modified tests on all VM configurations so I can quickly see which behaviour or return codes are commonly correct. In some cases, this lets me determine in which version some expected behaviour changed. This all started with the font family registry value MR. I wanted to check the value name on XP, since I thought it was correct but couldn’t be certain. That’s when I discovered the tests weren’t running and decided to see how much effort it would take to fix them. I know the value of these patches isn’t worth much, but I still find them useful. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1899#note_20678

1 0

[PATCH v4 0/1] MR1934: conhost.exe: Initialize colop_map when creating an alternate screen buffer.
by eric pouech (＠epo) 11 Jan '23

11 Jan '23

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54287 Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> -- v4: conhost.exe: Initialize color_map when creating an alternate screen buffer. https://gitlab.winehq.org/wine/wine/-/merge_requests/1934

3 2

[PATCH v3 0/1] MR1934: conhost.exe: Initialize colop_map when creating an alternate screen buffer.
by eric pouech (＠epo) 11 Jan '23

11 Jan '23

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54287 Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> -- v3: conhost.exe: Initialize colop_map when creating an alternate screen buffer. https://gitlab.winehq.org/wine/wine/-/merge_requests/1934

3 3

Re: [PATCH v2 0/4] MR1899: kernel32/tests: Call newer functions not on Windows XP or 2003 via function addresses (process)
by Alexandre Julliard (＠julliard) 11 Jan '23

11 Jan '23

> I don't see the maintenance cost or burden as high, nor do I mind monitoring this, if that's a concern. Seeing the number of patches you had to write (and will have to continue to write on an ongoing basis), I'd say the cost is significant. What's the upside? What behavior do you need to test on XP, and why? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1899#note_20671

1 0

Re: [PATCH v2 0/4] MR1899: kernel32/tests: Call newer functions not on Windows XP or 2003 via function addresses (process)
by Hugh McMaster (＠hmc) 11 Jan '23

11 Jan '23

I don't see the maintenance cost or burden as high, nor do I mind monitoring this, if that's a concern. Looking at recent test patches, I can see function addresses used. It's really only adding the macro part, then calling the pointer. Everything else is the same as normal. I think I'm actually to blame for the issues in the console tests... -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1899#note_20669

1 0

2025

2024

2023

2022

wine-gitlab