January 2024 - wine-gitlab

[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

[PATCH v4 0/6] MR4887: imm32: Test and fix WM_KEYUP events, CPS_CANCEL, CPS_COMPLETE and open status.
by Rémi Bernon (＠rbernon) 24 Jan '24

24 Jan '24

-- v4: imm32: Complete the composition string when the IME is closed. imm32/tests: Test the effect of CPS_CANCEL and CPS_COMPLETE. win32u: Also pass WM_KEYUP messages to ImmProcessKey. imm32/tests: Test that WM_KEYUP are passed to ImeProcessKey. imm32: Mask the scancode before passing it to ImeToAsciiEx. imm32/tests: Adjust todo_wine for the new Wine CJK keyboard layouts. https://gitlab.winehq.org/wine/wine/-/merge_requests/4887

3 8

[PATCH v3 0/6] MR4887: imm32: Test and fix WM_KEYUP events, CPS_CANCEL, CPS_COMPLETE and open status.
by Rémi Bernon (＠rbernon) 24 Jan '24

24 Jan '24

-- v3: imm32: Complete the composition string when the IME is closed. imm32/tests: Test the effect of CPS_CANCEL and CPS_COMPLETE. win32u: Also pass WM_KEYUP messages to ImmProcessKey. imm32/tests: Test that WM_KEYUP are passed to ImeProcessKey. imm32: Mask the scancode before passing it to ImeToAsciiEx. imm32/tests: Adjust todo_wine for the new Wine CJK keyboard layouts. https://gitlab.winehq.org/wine/wine/-/merge_requests/4887

3 9

[PATCH 0/3] MR595: vkd3d-shader/dxil: Implement DX intrinsics Cos, Sin and Tan.
by Conor McCarthy (＠cmccarthy) 24 Jan '24

24 Jan '24

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

2 3

[PATCH 0/3] MR4927: windows.gaming.input: Stub IRawGameController2 interface.
by Rémi Bernon (＠rbernon) 24 Jan '24

24 Jan '24

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

2 3

[PATCH v3 0/1] MR4926: Adapter test
by John H. Freeman (＠tingling0072) 24 Jan '24

24 Jan '24

-- v3: added test_GetAdaptersAddressesSizeZeroParam https://gitlab.winehq.org/wine/wine/-/merge_requests/4926

2 1

[PATCH v5 0/1] MR263: vkd3d-shader/spirv: Refactor the type system.
by Conor McCarthy (＠cmccarthy) 24 Jan '24

24 Jan '24

Shader Model 6 introduces a 16-bit float (half) type, and 16-bit and 64-bit integer types. Storing extra info in the type enum simplifies checking if a type is any integer, floating point or numeric type, and the declaration of SPIR-V types. The benefits depend on using enum vkd3d_data_type in the backend instead of vkd3d_shader_component_type. Patch 2 is difficult to split because types typically flow through to vkd3d_spirv_get_type_id(), so partial changes would require new calls to conversion functions which would be deleted again later. -- v5: vkd3d-shader/spirv: Use enum vkd3d_data_type instead of vkd3d_shader_component_type. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/263

3 3

[PATCH v2 0/3] MR4926: Adapter test
by John H. Freeman (＠tingling0072) 24 Jan '24

24 Jan '24

-- v2: updated comment before test to more accurately reflect https://gitlab.winehq.org/wine/wine/-/merge_requests/4926

4 7

2025

2024

2023

2022

wine-gitlab January 2024