December 2023 - Wine-GitLab

Re: [PATCH v2 0/1] MR4681: comctl32/tests: Store old DPI awareness context. - approved
by Alexandre Julliard (＠julliard) Dec. 12, 2023

Dec. 12, 2023

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4681

1 0

Re: [PATCH v2 0/1] MR4651: winewayland.drv: Avoid transient deactivation of foreground thread. - approved
by Alexandre Julliard (＠julliard) Dec. 12, 2023

Dec. 12, 2023

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4651

1 0

Re: [PATCH v2 0/1] MR4660: gdiplus: Fix invalid pointer returned when failing to create font - approved
by Alexandre Julliard (＠julliard) Dec. 12, 2023

Dec. 12, 2023

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4660

1 0

Re: [PATCH v2 0/1] MR4678: winebus: Return backend init status from bus_main_thread_start. - approved
by Alexandre Julliard (＠julliard) Dec. 12, 2023

Dec. 12, 2023

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4678

1 0

Re: [PATCH v4 0/5] MR502: vkd3d-shader/d3d-asm: Add an "internal" mode for the ASM dumper. - approved
by Alexandre Julliard (＠julliard) Dec. 12, 2023

Dec. 12, 2023

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/502

1 0

Re: [PATCH v11 0/7] MR489: vkd3d-shader: Prepare for 64-bit integer support. - approved
by Alexandre Julliard (＠julliard) Dec. 12, 2023

Dec. 12, 2023

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/489

1 0

[PATCH v6 0/3] MR504: ci: Validate the SPIR-V code.
by Giovanni Mascellani (＠giomasce) Dec. 12, 2023

Dec. 12, 2023

In order to validate SPIR-V code we have to fix a little bug that causes us to emit invalid SPIR-V code in some cases. That's technically a bug, so it should be good to fix it in 1.10; unfortunately the way the bug is fixed right now is not ideal, because in some cases it causes many push constants to be wasted, potentially reaching the Vulkan implementation limit, so some application that used to work might stop working. Eventually we should implement a better allocator for push constants, and include an alternative path if the Vulkan implementation doesn't offer enough push constants. -- v6: ci: Build vkd3d with SPIRV-Tools. vkd3d-shader/spirv: Honor force_validation after emitting SPIR-V code. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/504

2 4

[PATCH v5 0/3] MR504: ci: Validate the SPIR-V code.
by Giovanni Mascellani (＠giomasce) Dec. 12, 2023

Dec. 12, 2023

In order to validate SPIR-V code we have to fix a little bug that causes us to emit invalid SPIR-V code in some cases. That's technically a bug, so it should be good to fix it in 1.10; unfortunately the way the bug is fixed right now is not ideal, because in some cases it causes many push constants to be wasted, potentially reaching the Vulkan implementation limit, so some application that used to work might stop working. Eventually we should implement a better allocator for push constants, and include an alternative path if the Vulkan implementation doesn't offer enough push constants. -- v5: ci: Build vkd3d with SPIRV-Tools. vkd3d-shader/spirv: Honor force_validation after emitting SPIR-V code. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/504

4 6

[PATCH v7 0/2] MR4545: mf: Fix restarting a paused media session.
by Yuxuan Shui (＠yshui) Dec. 12, 2023

Dec. 12, 2023

-- v7: mf: Only preroll when starting from stopped state. mf/tests: Add test cases for evr events. https://gitlab.winehq.org/wine/wine/-/merge_requests/4545

3 10

[PATCH 0/4] MR473: tests/shader-runner: Run SM1 compilation in the shader runner, part 1.
by Francisco Casas (＠fcasas) Dec. 12, 2023

Dec. 12, 2023

Like the previous MRs, this has the objective of: * Preparing the way for SM1-specific tests. * Running SM1 compilation tests, even if we don't have a runner available to execute them (yet). * Allowing different runners to run through the shader_test file several times, targeting different shader model ranges. The current plan is: * We won't separate compilation tests from execution tests as in !418. * Instead of naming individual shader models in the shader_test files as in !434, we will keep working with the shader model ranges provided in the [require] directives. * We will test SM1 compilation going through the shader_test file twice with the vulkan runner, one for SM1 models and other for SM4 models, and for now we will just give a "todo" for execution tests until they are implemented (@zfigura patches). This first part only includes facilities to properly mark SM1-specific tests (as required by !458) and some refactoring to better work with the idea of intersecting shader model ranges. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/473

5 21