February 2024 - Wine-GitLab

[PATCH 0/5] MR5059: mfreadwrite/reader: Repeat pushing / pulling samples while it succeeds.
by Rémi Bernon Feb. 16, 2024

Feb. 16, 2024

First part of some refactor to implement the source reader pipeline. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5059

2 6

[PATCH v15 0/3] MR5081: dmime: Read through a MIDI file
by Yuxuan Shui (＠yshui) Feb. 16, 2024

Feb. 16, 2024

Add a dummy track parser, that reads through MIDI tracks and events. To make sure we understand the file structure correctly, no actual tracks or events are generated. Also add test cases to make sure we read through a MIDI file correctly. This is skeleton of the actual MIDI parser. Pending on the merge of !4982 -- v15: dmime/tests: Improve error reporting from expect_track. dmime: Read through a MIDI file. dmime: Don't skip chunk for MIDI files. https://gitlab.winehq.org/wine/wine/-/merge_requests/5081

3 11

Re: [PATCH v11 0/6] MR569: tests/shader_runer: Support SRV buffers. - approved
by Zebediah Figura (＠zfigura) Feb. 16, 2024

Feb. 16, 2024

This merge request was approved by Zebediah Figura. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/569

1 0

[PATCH v4 0/3] MR4987: ntdll: Support generic xstate (part 1).
by Paul Gofman (＠gofman) Feb. 16, 2024

Feb. 16, 2024

This is a preparation for supporting more xstate features in the contexts. The remaining parts are: - support arbitrary xstate in usr1_handler(); - support arbitrary xstate in the server contexts (probably transferring only the present part); - support arbitrary xstate in context manipulation functions; - enabling more xstates in system.c and in user shared data. -- v4: ntdll: Don't hardcode xstate size in exception stack layout. ntdll: Don't hardcode xstate size in syscall frame. ntdll: Don't hardcode xstate feature mask. https://gitlab.winehq.org/wine/wine/-/merge_requests/4987

2 4

[PATCH v3 0/3] MR4987: ntdll: Support generic xstate (part 1).
by Paul Gofman (＠gofman) Feb. 16, 2024

Feb. 16, 2024

This is a preparation for supporting more xstate features in the contexts. The remaining parts are: - support arbitrary xstate in usr1_handler(); - support arbitrary xstate in the server contexts (probably transferring only the present part); - support arbitrary xstate in context manipulation functions; - enabling more xstates in system.c and in user shared data. -- v3: ntdll: Don't hardcode xstate size in exception stack layout. ntdll: Don't hardcode xstate size in syscall frame. ntdll: Don't hardcode xstate feature mask. https://gitlab.winehq.org/wine/wine/-/merge_requests/4987

4 6

[PATCH v10 0/6] MR569: tests/shader_runer: Support SRV buffers.
by Francisco Casas (＠fcasas) Feb. 16, 2024

Feb. 16, 2024

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. -- v10: vkd3d-shader/hlsl: Parse Buffer types. tests/shader-runner: Change probe directive syntax on shader_test files. tests/shader-runner: Change resource declaration syntax on shader_test files. tests/shader-runner: Support SRV buffers. tests/shader-runner: Separate resource_type into type and dimension. vkd3d-shader/hlsl: Record valid methods in object_methods[]. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/569

2 6

[PATCH v11 0/3] MR741: ntdll: Implement NtFlushProcessWriteBuffers.
by Torge Matthies (＠tmatthies) Feb. 16, 2024

Feb. 16, 2024

Based on [a patch](https://www.winehq.org/mailman3/hyperkitty/list/wine-devel(a)winehq.… by Jinoh Kang (@iamahuman) from February 2022. I removed the need for the event object and implemented fast paths for Linux. On macOS 10.14+ `thread_get_register_pointer_values` is called on every thread of the process. On Linux 4.14+ `membarrier(MEMBARRIER_CMD_GLOBAL_EXPEDITED, ...)` is used. On x86 Linux <= 4.13 and on other platforms `madvise(..., MADV_DONTNEED)` is used, which sends IPIs to all cores causing them to do a memory barrier. -- v11: ntdll: Add thread_get_register_pointer_values-based implementation of NtFlushProcessWriteBuffers. ntdll: Add sys_membarrier-based implementation of NtFlushProcessWriteBuffers. ntdll: Add MADV_DONTNEED-based implementation of NtFlushProcessWriteBuffers. https://gitlab.winehq.org/wine/wine/-/merge_requests/741

3 10

[PATCH v4 0/3] MR629: vkd3d-shader/dxil: Implement DX intrinsic GetDimensions.
by Conor McCarthy (＠cmccarthy) Feb. 16, 2024

Feb. 16, 2024

-- v4: vkd3d-shader/dxil: Implement DX intrinsic GetDimensions. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/629

2 3

[PATCH 0/5] MR5078: wined3d: Dynamic pipeline state, part 1.
by Zebediah Figura (＠zfigura) Feb. 16, 2024

Feb. 16, 2024

This includes viewport and scissor rect (core in 1.0), and depth/stencil state (comprised entirely of elements in EXT_extended_dynamic_state). Further patches add other dynamic state extensions and make other parts of the pipeline state dynamic. Theoretically dynamic state should be an improvement, giving greater freedom to the driver and hardware to optimize, and (perhaps more importantly) reducing the time needed to look up and compile new pipeline states. In practice I haven't observed a clear and measureable difference in either performance or stutter; however, my testing has been extremely scarce. Note: This patch series in particular introduces a new validation warning which prints on almost every draw. The warning is described at [1]. Similar warnings are triggered by future patches making other parts of the pipeline state dynamic. An unfortunately internal Khronos discussion has determined that the warning is undesirable, and there is currently motion to adjust the specification accordingly; however, the validation layers have not yet been adjusted. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5078

4 7

Re: [PATCH v5 0/2] MR583: vkd3d-shader/dxil: SRV/UAV support part 2.
by Giovanni Mascellani (＠giomasce) Feb. 16, 2024

Feb. 16, 2024

Giovanni Mascellani (@giomasce) commented about libs/vkd3d-shader/dxil.c: > [DX_LEGACY_F32TOF16 ] = {"i", "f", sm6_parser_emit_dx_unary}, > [DX_LOAD_INPUT ] = {"o", "ii8i", sm6_parser_emit_dx_load_input}, > [DX_LOG ] = {"g", "R", sm6_parser_emit_dx_unary}, > + [DX_RAW_BUFFER_LOAD ] = {"o", "Hii8i", sm6_parser_emit_dx_raw_buffer_load}, I just realized that the last parameter is never read. Is that intended? What is supposed to be there? Maybe you could add a comment in the code to explain this? Apparently something similar happens for `DX_LOAD_INPUT` too and maybe other DX opcodes. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/583#note_61454

1 0