January 2024 - wine-gitlab

[PATCH 0/1] MR4928: ntdll: Fix building for ARM with libunwind enabled.
by Martin Storsjö (＠mstorsjo) 24 Jan '24

24 Jan '24

The references to raise_func_trampoline were left behind in 89f3c59739e6a879b6f362dfd29d41347590449d. In Linux builds, libunwind isn't practically needed since a27b202a4ddc314e3e856c10f2e5d010c4a88ee0 (which implemented an internal EHABI unwinder). However if the internal EHABI support is skipped (as it would be if building on an OS different than Linux), libunwind doesn't seem to be able to unwind properly through all cases after the changes in commits 5b068472141, 75d0d466ec9 and 89f3c59739e any longer, in a non-PE build. Signed-off-by: Martin Storsjö <martin(a)martin.st> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4928

3 5

[PATCH v3 0/6] MR545: vkd3d: Assorted fixes for MoltenVK, part 2.
by Giovanni Mascellani (＠giomasce) 24 Jan '24

24 Jan '24

The rest is in MR !531. -- v3: tests: Mark count buffers as buggy on MoltenVK. tests: Mark a timestamp query test as buggy on MoltenVK. tests: Mark clip distance as unsupported on MoltenVK. tests: Mark cull distance as buggy on MoltenVK. tests: Skip unbounded descriptor ranges tests when they're unsupported. tests: Mark loading from stencil as buggy on MoltenVK. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/545

3 7

[PATCH 0/1] MR4929: ntdll: Reduce fixme logging for large numbers of cores.
by Martin Storsjö (＠mstorsjo) 24 Jan '24

24 Jan '24

Once we've reached the condition for skipping a core, we will skip all other cores in the same range as well - don't print a fixme message for each of them. Signed-off-by: Martin Storsjö <martin(a)martin.st> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4929

2 2

[PATCH 0/3] MR4915: d3d9: Implement Direct3DCreate9On12().
by Mohamad Al-Jaf (＠maljaf) 24 Jan '24

24 Jan '24

Needed by Orbiter Space Flight Simulator and Train Simulator Classic. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4915

5 12

[PATCH v3 0/1] MR4912: winex11.drv: Fix wglSwapBuffers() with NULL current context with child window rendering.
by Paul Gofman (＠gofman) 24 Jan '24

24 Jan '24

After wglMakeCurrent(NULL, NULL); wglSwapBuffers(HDC) actually swaps buffers for the device context. That works on Windows and basically with Wine glx (as glxSwapBuffers also works on drawable and doesn't need GLX context). But that doesn't work for child window rendering: first because of NULL ctx dereference (checked for NULL elsewhere) and next because of GLX_OML_sync_control path. Fixes Black Desert Online launcher being black screen. The launcher does the following for drawing a frame (while drawing on the child window): ``` wglMakeCurrent(hdc, valid context); <gl drawing> wglMakeCurrent(NULL, NULL); wglSwapBuffers(hdc); ``` -- v3: winex11.drv: Fix wglSwapBuffers() with NULL current context with child window rendering. https://gitlab.winehq.org/wine/wine/-/merge_requests/4912

4 4

[PATCH v2 0/2] MR588: vkd3d-shader: Introduce VKD3D_SHADER_COMPILE_OPTION_FEATURE_FLOAT64.
by Conor McCarthy (＠cmccarthy) 24 Jan '24

24 Jan '24

-- v2: vkd3d-shader/spirv: Check for FEATURE_FLOAT64 when double precision use is flagged. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/588

3 3

[PATCH v3 0/4] MR584: vkd3d-shader/dxil: Support for isinf, isnan and isfinite.
by Conor McCarthy (＠cmccarthy) 24 Jan '24

24 Jan '24

-- v3: vkd3d-shader/spirv: Handle the ISINF and ISNAN instructions in spirv_compiler_emit_alu_instruction(). vkd3d-shader/spirv: Implement the ISFINITE instruction. tests/shader-runner: Add tests for floating point special values. vkd3d-shader/dxil: Handle floating point special value comparisons in sm6_parser_emit_dx_unary(). https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/584

3 5

[PATCH v7 0/5] MR561: vkd3d-utils: D3DReflect() and reflection tests, part 1/2.
by Zebediah Figura (＠zfigura) 24 Jan '24

24 Jan '24

Unlike previous vkd3d-utils interfaces, ID3D12ShaderReflection is rather more large and complex, and will probably end up needing several new individual scan interfaces from vkd3d-shader, which are themselves not exactly trivial to design. Therefore, instead of implementing everything in vkd3d-shader and then hooking up the vkd3d-utils interfaces on top of that, this patch series copies the existing implementation of reflection and then begins the process of moving its implementation to vkd3d-shader. The primary motivation here is to add reflection crosstests (primarily for the benefit of the HLSL compiler) without being blocked on API design. Part 2 of this patch series does this. -- v7: tests: Test signature reflection via D3DReflect(). https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/561

3 7

[PATCH v17 0/5] MR514: tests: Use the vulkan runner to run SM1 compilation tests.
by Francisco Casas (＠fcasas) 24 Jan '24

24 Jan '24

Recap: My previous proposals to extend the shader_runner to SM1 were focusing on separating compilation tests ([shader] directives) from execution tests ([test] directives), and let the generic shader_runner.c:compile_shader() in charge of the former. However, Henri was more inclined to aim for making the parser agnostic to the language of the tests so we can potentially extend the shader_runner tests to other languages such as d3d-asm. This means, removing the burden of compilation from the parser altogether, and moving it to the runners, probably through a runner->compile function pointer (even if most of them end up doing the same thing, compiling with vkd3d-shader or the native compiler, depending on availability). Agreeing with going in this general direction, this MR contains patches to do SM1 compilation calling run_shader_tests() for SM1 profiles from the Vulkan runner (skipping execution for now), and some improvements to the qualifiers syntax. Despite this, there are parallel discussions on: - Whether to name the shader models individually in the [require] directives or expressing the range of shader models where the test should pass. In the latter case, whether to run for all shader models, only the lowest one in the SM1, SM4, and SM6 groups, or to allow the runner to select a shader model within the range (I feel strongly against this now, I think the runner should just retrieve a boolean in runner->check_requirements). - Where to do the iteration across different shader models, if in run_shader_tests() or expect each runner to call run_shader_tests() several times as we do now. But there is no need to settle on something for these yet. --- Now, what may be the most noisy part of this MR is that even though we are calling run_shader_tests() through the Vulkan runner, this will result in calling shader_runner.c:compile_shader() instead of shader_runner_vulkan.c:compile_shader(), but if we follow the "making the parser agnostic" plan, we eventually should get rid of shader_runner.c:compile_shader() and introduce the runner->compile pointer instead. -- v17: tests: Use the vulkan runner to run SM1 compilation tests. vkd3d-shader/ir: Lower texkill instructions to discard_nz. vkd3d-shader/d3dbc: Emit fixme for HLSL_RESOURCE_SAMPLE_LOD. tests/shader-runner: Call each runner only once. tests/shader-runner: Support reading multiple model range args for qualifiers. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/514

3 7

[PATCH v3 0/3] MR569: tests/shader_runer: Support SRV buffers.
by Francisco Casas (＠fcasas) 24 Jan '24

24 Jan '24

This allows to declare SRV buffers in the shader tests using `[buffer srv n]` blocks, and passing them to the different backends. Also, 1/2 includes a missing bit required to parse `Buffer<>` types in the HLSL compiler. This is a step towards supporting StructuredBuffer types in further patches. -- v3: tests/shader_runner: Support SRV buffers. tests/shader-runner: Override resource types of the same category. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/569

4 10

2025

2024

2023

2022

wine-gitlab January 2024