- wine-gitlab - winehq.org

[PATCH 0/5] MR5135: Explicitly request debug info in critical sections.
by Paul Gofman (＠gofman) 23 Feb '24

23 Feb '24

See https://gitlab.winehq.org/wine/wine/-/merge_requests/5071 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5135

3 6

[PATCH 0/2] MR675: Draft: tests/shader-runner: Add a raw UAV test.
by Conor McCarthy (＠cmccarthy) 23 Feb '24

23 Feb '24

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

2 2

[PATCH v7 0/8] MR662: vkd3d-shader/ir: Introduce a better CFG structurizer, part 2.
by Giovanni Mascellani (＠giomasce) 23 Feb '24

23 Feb '24

~~This applies on top of !656, the last three commits belong here.~~ -- v7: vkd3d-shader/ir: Sort each loop by block label. vkd3d-shader/ir: Dump the loops in the control flow graph. vkd3d-shader/ir: Keep track of loops by header block. vkd3d-shader/ir: Keep a reference to the parser inside struct vsir_cfg. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/662

3 11

Re: [PATCH v18 0/5] MR564: vkd3d-shader/ir: Transform clip/cull signature elements into an array.
by Conor McCarthy (＠cmccarthy) 23 Feb '24

23 Feb '24

On Thu Feb 22 14:13:20 2024 +0000, Giovanni Mascellani wrote: > Can this happen? Unless I'm missing something, it seems that for domain > shaders `normaliser_signature_transform_clip_cull()` is never called, so > `has_normalised_clip_cull` is never set and the normaliser returns > before reaching here. I moved it to the next commit, where `normaliser_signature_transform_clip_cull()` is called on other signatures. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/564#note_62426

1 0

[PATCH v17 0/5] MR564: vkd3d-shader/ir: Transform clip/cull signature elements into an array.
by Conor McCarthy (＠cmccarthy) 23 Feb '24

23 Feb '24

-- v17: tests/d3d12: Test multiple clip distance inputs in test_clip_distance(). tests/d3d12: Use five clip distances for the multiple test in test_clip_distance(). vkd3d-shader/ir: Transform clip/cull outputs and patch constants into arrays. vkd3d-shader/ir: Transform clip/cull inputs into an array. vkd3d-shader/spirv: Support no-op signature elements. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/564

4 11

[PATCH v6 0/8] MR662: vkd3d-shader/ir: Introduce a better CFG structurizer, part 2.
by Giovanni Mascellani (＠giomasce) 23 Feb '24

23 Feb '24

~~This applies on top of !656, the last three commits belong here.~~ -- v6: vkd3d-shader/ir: Sort each loop by block label. vkd3d-shader/ir: Dump the loops in the control flow graph. vkd3d-shader/ir: Keep track of loops by header block. vkd3d-shader/ir: Keep a reference to the parser inside struct vsir_cfg. vkd3d-shader/ir: Compute the loops in the control flow graph. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/662

3 13

[PATCH v2 0/3] MR5141: dmime: bandtrack for MIDI files
by Yuxuan Shui (＠yshui) 23 Feb '24

23 Feb '24

Create a bandtrack for MIDI files by picking out the MIDI 0xCn events, and creating matching DMUS_PATCH_PMSG. * * * This also has a commit adding a stub chordtrack, which is small so I think a separate MR is unwarranted. Can be split out if necessary. -- v2: dmime: Add a stub chordtrack for MIDI segments. dmime: Parse MIDI program change events and generate a bandtrack. https://gitlab.winehq.org/wine/wine/-/merge_requests/5141

2 3

[PATCH 0/1] MR5140: wbemprox: Protect tables with a critical section.
by Hans Leidekker (＠hans) 23 Feb '24

23 Feb '24

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56334 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5140

2 1

[PATCH 0/1] MR666: vkd3d-shader/hlsl: Allow modifiers on buffer declarations.
by Nikolay Sivov (＠nsivov) 23 Feb '24

23 Feb '24

Buffers could be used with 'shared' and 'single' modifiers. There is a bit more work left to do to support this - 'shared' needs a compiler flag to enable child effects to be useful, and 'single' is not a keyword. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/666

4 3

[PATCH v2 0/2] MR661: Draft: tests: Introduce custom test driver.
by Francisco Casas (＠fcasas) 23 Feb '24

23 Feb '24

Basically !427, but in the form of a custom test driver script. If I am not mistaken, for the driver script to run properly it is necessary to run "autoreconf" in the source directory and call the configure script again in the build directory. The output when running tests would be the same we currently have except for tests that don't PASS, in that case, detailed information for each failing line will appear. Make a failing test to try it! -- v2: tests: Get detailed information on failing tests. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/661

3 5

2025

2024

2023

2022

wine-gitlab