December 2023 - Wine-GitLab

[PATCH v3 0/1] MR523: vkd3d: Use mutable descriptors if available.
by Conor McCarthy (＠cmccarthy) Dec. 18, 2023

Dec. 18, 2023

-- v3: vkd3d: Use mutable descriptors if available. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/523

2 1

[PATCH 0/1] MR4708: winedbg: Retrieve architecture from process.
by Bernhard Übelacker Dec. 18, 2023

Dec. 18, 2023

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

2 4

[PATCH 0/2] MR4714: server: Ignore the capture window wrt desktop cursor changes.
by Rémi Bernon Dec. 18, 2023

Dec. 18, 2023

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55306 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56046 I am tempted to drop the always_queue logic entirely, and always merge/queue the mouse move messages, but that would be a bigger change. This is enough to fix both regressions (the original with Worms Armageddon and the new one with Pegasus Mail). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4714

1 2

[PATCH 0/1] MR4713: include: Add missing macros in devenum.idl
by Biswapriyo Nath (＠Biswa96) Dec. 18, 2023

Dec. 18, 2023

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

3 2

[PATCH 0/1] MR4676: server: Check whether the cursor has been set for a thread input.
by Rémi Bernon Dec. 18, 2023

Dec. 18, 2023

We are preferring the thread input cursor over the global desktop cursor, but if the thread input has no cursor yet, for instance when thread is attached to another thread without a message queue yet, it will end up being invisible. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55961 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4676

1 2

[PATCH 0/1] MR4710: winedbg: Add wow option in info share usage.
by Bernhard Übelacker Dec. 18, 2023

Dec. 18, 2023

This patch just adds to the usage the "wow" keyword, which causes all modules to be listed instead of just the ones of the process executables architecture. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4710

2 4

[PATCH 0/2] MR4712: Speed-up and fix for dbghelp.SymLoadModule().
by eric pouech (＠epo) Dec. 18, 2023

Dec. 18, 2023

Some games exhibit freeze in game play because they implement something like: - upon an event (exception...) - use toolhelp to get a snapshot of self loaded modules, - call SymLoadModule() on each module, - furthermore, they keep their dbghelp session active, and redo the process above when a new event occurs. This ends up with trying to reload at the very same base address each one of the already loaded modules. Native implements a fast exit path when asking to load a module at the exact same base address of an already loaded one: it simply bails out (without checking anything else). Builtin is way more slow (it resync:s ELF/Mach-o module list, load the new module before actually dropping at the end of the process). This can result in second of relay. This serie adds the tests for supporting above claim and fix it. Credit to Paul Gofman for triaging this behavior. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4712

2 2

[PATCH 0/2] MR527: vkd3d-shader: Implement I/O for shader model 2.
by Zebediah Figura (＠zfigura) Dec. 18, 2023

Dec. 18, 2023

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

2 2

[PATCH 0/2] MR4711: Fix Toad for Oracle F3 find next function not working properly
by Zhiyi Zhang (＠zhiyi) Dec. 18, 2023

Dec. 18, 2023

Fix Toad for Oracle F3 find next function not working properly because its WH_KEYBOARD hook gets called too many times. There is another case that could cause WH_CBT HCBT_CLICKSKIPPED hooks to get called recursively as the tests show. I will send patches for that after the code freeze. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4711

2 2

Re: [PATCH v8 0/6] MR3288: Draft: gdiplus: Clip polygons before drawing them
by David Kahurani (＠kahurani) Dec. 17, 2023

Dec. 17, 2023

Superceded by !4206 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56170

1 0

Re: [PATCH v8 0/6] MR3288: Draft: gdiplus: Clip polygons before drawing them - closed
by David Kahurani (＠kahurani) Dec. 17, 2023

Dec. 17, 2023

This merge request was closed by David Kahurani. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288

1 0

[PATCH v3 0/1] MR4306: rpcrt4/tests: Use CRT allocation functions.
by Alex Henrie (＠alexhenrie) Dec. 16, 2023

Dec. 16, 2023

-- v3: rpcrt4/tests: Use CRT allocation functions. https://gitlab.winehq.org/wine/wine/-/merge_requests/4306

3 2

Re: [PATCH v8 0/6] MR3288: Draft: gdiplus: Clip polygons before drawing them
by Esme Povirk (＠madewokherd) Dec. 16, 2023

Dec. 16, 2023

On Sat Dec 16 08:27:12 2023 +0000, David Kahurani wrote: > "I don't believe draw_poly is the right place for this. Either > optimizations should be in gdi32, or in SOFTWARE_GdipFillPath (which we > don't use now for drawing outlines because the gdi32 path is currently > more efficient, but we could if that changed)." > Looking at this again, it looks like we should try to re-implement > SOFTWARE_GdipFillPath to allow for drawing outlines. Maybe add a flag > for whether we need to outline only and when we need to fill it? We have a special case for drawing 1-pixel outlines. In other cases, the way to do that is by generating a path for the outline with GdipWidenPath and filling that. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56161

1 0

[PATCH 0/1] MR4706: vulkan-1/tests: Enable feature in private data test.
by Georg Lehmann (＠DadSchoorse) Dec. 16, 2023

Dec. 16, 2023

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

2 1

Re: [PATCH v8 0/6] MR3288: Draft: gdiplus: Clip polygons before drawing them
by David Kahurani (＠kahurani) Dec. 16, 2023

Dec. 16, 2023

On Fri Dec 15 16:56:08 2023 +0000, Esme Povirk wrote: > My thinking is that we will eventually need to implement an equivalent > for `GdipGetRegionHrgn` that returns some raw data instead of an HRGN, > and more importantly optimizes generally for known bounding boxes (this > would include the Graphics bounding box as well as its clip region). See > https://gitlab.winehq.org/wine/wine/-/merge_requests/4206 for some of my > initial work on that. > If we do the translation outside of gdi32, we can do it by scanline and > treat the path as a set of independent line segments. We can then ignore > scanlines and line segments outside of our output range. I think > `create_polypolygon_region` in win32 does something similar, but sadly I > don't think there's a way to pass in a value for `clip_rect` from the outside. "I don't believe draw_poly is the right place for this. Either optimizations should be in gdi32, or in SOFTWARE_GdipFillPath (which we don't use now for drawing outlines because the gdi32 path is currently more efficient, but we could if that changed)." Looking at this again, it looks like we should try to re-implement SOFTWARE_GdipFillPath to allow for drawing outlines. Maybe add a flag for whether we need to outline only and when we need to fill it? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56152

1 0

[PATCH v5 0/6] MR4082: gdiplus: Implement font linking in GdipDrawString.
by Santino Mazza (＠tati1454) Dec. 15, 2023

Dec. 15, 2023

-- v5: gdiplus: Implement font linking for gdiplus. gdiplus/tests: Add interactive test for font linking. mlang: Fix bug with codepage priority in GetStrCodePages. mlang/tests: Test codepages priority bug in GetStrCodepages. mlang: Implement GetGlobalFontLinkObject. mlang/tests: Test for GetGlobalFontLinkObject. https://gitlab.winehq.org/wine/wine/-/merge_requests/4082

3 18

[PATCH 0/1] MR4705: ntdll: Use position independent syscall thunk for NtQueryInformationProcess on i386.
by Paul Gofman (＠gofman) Dec. 15, 2023

Dec. 15, 2023

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55967 Fixes a regression introduced by commit efd03f40e6e315d89cd1d09c48180aae82033f9f. The app reads syscall thunk for NtQueryInformationProcess() from ntdll file and just calls that from some memory location. That worked before the referenced commit because without performing relocations that was jumping to wine_syscall in the loaded ntdll.dll. Now when the actual ntdll load address is different that jumps to the same address which is now non sensual. The existing tests show that in general 32-bit syscall thunks need relocation. The same trick with some other Nt functions I tried doesn't work on Windows, but turns out NtQueryInformationProcess is special (the included test replicates that). The form of syscall thunk I used in the patch corresponds to what was in Wine-Staging before the upsream implementation of syscall thunks (that is, call to NtCurrentTeb()->WOW32Reserved). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4705

2 1

[PATCH v3 0/5] MR463: hlsl: Fix some type handling for ternaries.
by Zebediah Figura (＠zfigura) Dec. 15, 2023

Dec. 15, 2023

-- v3: vkd3d-shader/hlsl: Allow non-numeric types in the ternary operator. vkd3d-shader/hlsl: Separate an add_ternary() helper. tests: Add many more tests for ternary expressions. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/463

3 13

Re: [PATCH v2 0/1] MR4695: winewayland.drv: Support mouse buttons 4 and 5. - approved
by Alexandre Julliard (＠julliard) Dec. 15, 2023

Dec. 15, 2023

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

1 0

Re: [PATCH v3 0/1] MR4679: winewayland.drv: Release all keys on keyboard focus loss. - approved
by Alexandre Julliard (＠julliard) Dec. 15, 2023

Dec. 15, 2023

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

1 0

Re: [PATCH v6 0/2] MR3405: server: Use the capture window as cursor window if it is set. - approved
by Alexandre Julliard (＠julliard) Dec. 15, 2023

Dec. 15, 2023

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

1 0

Re: [PATCH v2 0/1] MR4701: kernel32/tests: Fix ProcessMachineTypeInfo tests. - approved
by Alexandre Julliard (＠julliard) Dec. 15, 2023

Dec. 15, 2023

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

1 0

Re: [PATCH v2 0/1] MR4700: po: Update Simplified Chinese translation. - approved
by Alexandre Julliard (＠julliard) Dec. 15, 2023

Dec. 15, 2023

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

1 0

[PATCH v3 0/2] MR4699: wined3d: Store the resource heap memory pointer directly.
by Rémi Bernon Dec. 15, 2023

Dec. 15, 2023

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55773 -- v3: wined3d: Store the resource heap memory pointer separately. wined3d: Add more padding to resource memory allocations. https://gitlab.winehq.org/wine/wine/-/merge_requests/4699

1 3

[PATCH v2 0/2] MR4699: wined3d: Store the resource heap memory pointer directly.
by Rémi Bernon Dec. 15, 2023

Dec. 15, 2023

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55773 -- v2: wined3d: Store the resource heap memory pointer directly. wined3d: Introduce a new wined3d_resource_get_sysmem helper. https://gitlab.winehq.org/wine/wine/-/merge_requests/4699

3 7

Re: [PATCH v8 0/6] MR3288: gdiplus: Clip polygons before drawing them
by Esme Povirk (＠madewokherd) Dec. 15, 2023

Dec. 15, 2023

On Fri Dec 15 16:05:24 2023 +0000, David Kahurani wrote: > I guess the way forward would be: > 1) Optimize `GdipGetRegionHrgn` in GDI+ which is done in this > MR(assuming we remove the last patch) > 2) Optimize `DrawPoly` in gdi32 My thinking is that we will eventually need to implement an equivalent for `GdipGetRegionHrgn` that returns some raw data instead of an HRGN, and more importantly optimizes generally for known bounding boxes (this would include the Graphics bounding box as well as its clip region). See https://gitlab.winehq.org/wine/wine/-/merge_requests/4206 for some of my initial work on that. If we do the translation outside of gdi32, we can do it by scanline and treat the path as a set of independent line segments. We can then ignore scanlines and line segments outside of our output range. I think `create_polypolygon_region` in win32 does something similar, but sadly I don't think there's a way to pass in a value for `clip_rect` from the outside. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56116

1 0

Re: [PATCH v8 0/6] MR3288: gdiplus: Clip polygons before drawing them
by Esme Povirk (＠madewokherd) Dec. 15, 2023

Dec. 15, 2023

Stopping my detailed review because I don't think this approach to optimizing the path is quite right. Suppose I fill a polygon that very closely approximates a circle, that this circle contains the entire bounding rectangle of the Graphics object, and that it does not intersect any edges of the bounding rectangle. That would mean that none of the individual points intersect the bounding rectangle. For a sufficiently close approximation, no set of 3 adjacent points in the polygon would intersect the bounding rectangle. If I understand correctly how `clip_path` is meant to work, it would remove every point except for the starting point, which would mean that nothing would be drawn, when instead the full bounding box of the Graphics object should be filled. I think that in order to fix this case, you would need to ignore any points not added to the output rectangle. So if I have a polygon that goes A B C D (with A being a start point and B C D being line points), and point B is removed, then you need to check points A, C, and D in order to determine whether point C can be removed. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56114

1 0

[PATCH 0/1] MR4703: dmime: Fix handling of curve PMSG.
by Yuxuan Shui (＠yshui) Dec. 15, 2023

Dec. 15, 2023

DMUS_PMSG::dwType is the type of the message, but we are comparing it to curve types. We should be using DMUS_CURVE_PMSG::bType instead. * * * (I tried to write some test cases for this. I created a IDirectMusicPort implementation that checks the generated midi commands, but instead I cannot get Windows to generate any midi commands for CCCURVEs. ) -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4703

3 5

Re: [PATCH v8 0/6] MR3288: gdiplus: Clip polygons before drawing them
by Esme Povirk (＠madewokherd) Dec. 15, 2023

Dec. 15, 2023

Esme Povirk (@madewokherd) commented about dlls/gdiplus/graphicspath.c: > + top = in->pathdata.Points[i + j].Y; > + > + if (in->pathdata.Points[i + j].Y > bottom) > + bottom = in->pathdata.Points[i + j].Y; > + } > + > + set_rect(&bounds, leftmost, top, rightmost - leftmost, bottom - top); > + > + /* properties of intersect rectangle */ > + leftmost = (rect.X < bounds.X) ? bounds.X : rect.X; > + top = (rect.Y < bounds.Y) ? bounds.Y : rect.Y; > + > + rightmost = (rect.X + rect.Width < bounds.X + bounds.Width) > + ? rect.X + rect.Width : bounds.X + bounds.Width; > + bottom = (rect.Y + rect.Height < bounds.Y + bounds.Height) > + ? rect.Y + rect.Height : bounds.Y + bounds.Height; I think using fminf/fmaxf functions would make this easier to read. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56108

1 0

[PATCH 0/3] MR4704: user32/tests: Fix and workaround some keyboard layout tests.
by Rémi Bernon Dec. 15, 2023

Dec. 15, 2023

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51478 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55327 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55328 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4704

2 5

[PATCH v7 0/6] MR3288: gdiplus: Clip polygons before drawing them
by David Kahurani (＠kahurani) Dec. 15, 2023

Dec. 15, 2023

Validate user data before passing it to PolyDraw. The program in the bug requests to draw figures outrageously outside the DC's region after presumably, some uninitialized values happen as a result of a missing font. Native gdiplus seems to handle this gracefully so we probably also should. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=41617 Signed-off-by: David Kahurani <k.kahurani(a)gmail.com> -- v7: gdiplus: Hook on optimized path drawing code gdiplus: Re-implement trace_path to avoid circular dependency gdiplus: Make get_region_hrgn public to gdiplus gdiplus: Clip polygons before drawing them gdiplus: Make get_graphis_device_bounds public to gdiplus gdiplus: Allow for writing nodes to an empty path points list https://gitlab.winehq.org/wine/wine/-/merge_requests/3288

4 10

Re: [PATCH v8 0/6] MR3288: gdiplus: Clip polygons before drawing them
by Esme Povirk (＠madewokherd) Dec. 15, 2023

Dec. 15, 2023

Esme Povirk (@madewokherd) commented about dlls/gdiplus/graphicspath.c: > memset(types + i, 0, ((path->pathdata.Count + 3) & ~3) - path->pathdata.Count); > return size; > } > + > +GpStatus clip_path(GpGraphics *graphics, GpPath *in, GpPath *out) > +{ > + RectF rect; > + int i; > + path_list_node_t *list, *pos = NULL; > + > + get_graphics_device_bounds(graphics, &rect); > + > + for (i = 1; i < in->pathdata.Count - 1; i++) > + { > + RectF bounds; I think it would be simpler to change `rect` to left/top/right/bottom values. I don't think this `bounds` variable should be needed at all. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56105

1 0

Re: [PATCH v8 0/6] MR3288: gdiplus: Clip polygons before drawing them
by Esme Povirk (＠madewokherd) Dec. 15, 2023

Dec. 15, 2023

Esme Povirk (@madewokherd) commented about dlls/gdiplus/graphicspath.c: > memset(types + i, 0, ((path->pathdata.Count + 3) & ~3) - path->pathdata.Count); > return size; > } > + > +GpStatus clip_path(GpGraphics *graphics, GpPath *in, GpPath *out) > +{ > + RectF rect; > + int i; > + path_list_node_t *list, *pos = NULL; `list` needs to be initialized to NULL. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56104

1 0

Re: [PATCH v8 0/6] MR3288: gdiplus: Clip polygons before drawing them
by David Kahurani (＠kahurani) Dec. 15, 2023

Dec. 15, 2023

On Fri Dec 15 16:05:24 2023 +0000, Esme Povirk wrote: > I don't believe `draw_poly` is the right place for this. Either > optimizations should be in gdi32, or in `SOFTWARE_GdipFillPath` (which > we don't use now for drawing outlines because the gdi32 path is > currently more efficient, but we could if that changed). I guess the way forward would be: 1) Optimize `GdipGetRegionHrgn` in GDI+ which is done in this MR(assuming we remove the last patch) 2) Optimize `DrawPoly` in gdi32 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56103

1 0

Re: [PATCH v8 0/6] MR3288: gdiplus: Clip polygons before drawing them
by Esme Povirk (＠madewokherd) Dec. 15, 2023

Dec. 15, 2023

Esme Povirk (@madewokherd) commented about dlls/gdiplus/graphicspath.c: > memset(types + i, 0, ((path->pathdata.Count + 3) & ~3) - path->pathdata.Count); > return size; > } > + > +GpStatus clip_path(GpGraphics *graphics, GpPath *in, GpPath *out) > +{ > + RectF rect; > + int i; > + path_list_node_t *list, *pos = NULL; > + > + get_graphics_device_bounds(graphics, &rect); I think it would be cleaner to have the caller pass in a rectangle to clip to. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56102

1 0

Re: [PATCH v8 0/6] MR3288: gdiplus: Clip polygons before drawing them
by Esme Povirk (＠madewokherd) Dec. 15, 2023

Dec. 15, 2023

Esme Povirk (@madewokherd) commented about dlls/gdiplus/graphics.c: > return Ok; > } > > -static GpStatus get_graphics_device_bounds(GpGraphics* graphics, GpRectF* rect) > +GpStatus get_graphics_device_bounds(GpGraphics* graphics, GpRectF* rect) Changing a static function to non-static shouldn't be in its own commit. You should combine it with the first commit that uses it outside its source file. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56101

1 0

Re: [PATCH v8 0/6] MR3288: gdiplus: Clip polygons before drawing them
by Esme Povirk (＠madewokherd) Dec. 15, 2023

Dec. 15, 2023

Esme Povirk (@madewokherd) commented about dlls/gdiplus/graphicspath.c: > * pointer on success > * NULL on allocation problems > */ > -static path_list_node_t* add_path_list_node(path_list_node_t *node, REAL x, REAL y, BOOL type) > +static path_list_node_t* add_path_list_node(path_list_node_t **node, REAL x, REAL y, BOOL type) > { > path_list_node_t *new; > > + if (!*node) > + { > + *node = calloc(1, sizeof(path_list_node_t)); All fields are immediately initialized below, so I think it's fine to use `malloc`. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3288#note_56100

1 0

[PATCH v3 0/1] MR4698: winewayland.drv: Add unaccelerated pointer support
by Grigory Vasilyev (＠h0tc0d3) Dec. 15, 2023

Dec. 15, 2023

Adds an env variable WINE_WAYLAND_UNACCELERATED_POINTER which allows raw input. This makes it easier to calculate the same sensitivity in different games, use sensitivity calculators, and easily change values when changing DPI and do not depend on the compositor or OS. For example, you want to set the sensitivity to half as much, and sensitivity curves in libinput are more difficult to calculate than in the games themselves. -- v3: winewayland.drv: Add unaccelerated pointer support https://gitlab.winehq.org/wine/wine/-/merge_requests/4698

4 9

[PATCH v6 0/6] MR3288: gdiplus: Clip polygons before drawing them
by David Kahurani (＠kahurani) Dec. 15, 2023

Dec. 15, 2023

Validate user data before passing it to PolyDraw. The program in the bug requests to draw figures outrageously outside the DC's region after presumably, some uninitialized values happen as a result of a missing font. Native gdiplus seems to handle this gracefully so we probably also should. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=41617 Signed-off-by: David Kahurani <k.kahurani(a)gmail.com> -- v6: gdiplus: Hook on optimized path drawing code gdiplus: Re-implement trace_path to avoid circular dependency gdiplus: Make get_region_hrgn public to gdiplus gdiplus: Clip polygons before drawing them gdiplus: Make get_graphis_device_bounds public to gdiplus gdiplus: Allow for writing nodes to an empty path points list https://gitlab.winehq.org/wine/wine/-/merge_requests/3288

3 7

[PATCH v15 0/7] MR450: vkd3d-shader/ir: Flatten structured control flow instructions.
by Conor McCarthy (＠cmccarthy) Dec. 15, 2023

Dec. 15, 2023

-- v15: vkd3d-shader/ir: Store code block names in struct vkd3d_shader_desc. vkd3d-shader/ir: Flatten SWITCH/CASE/DEFAULT/ENDSWITCH control flow instructions. vkd3d-shader/ir: Flatten LOOP/BREAK/CONTINUE/ENDLOOP control flow instructions. vkd3d-shader/ir: Flatten IF/ELSE/ENDIF control flow instructions. vkd3d-shader/spirv: Handle RETP in spirv_compiler_handle_instruction(). vkd3d-shader/spirv: Handle DISCARD and TEXKILL in spirv_compiler_handle_instruction(). vkd3d-shader/spirv: Emit descriptor offset loads in the function entry block. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/450

3 9

[PATCH v5 0/1] MR3288: gdiplus: Clip polygons before drawing them
by David Kahurani (＠kahurani) Dec. 15, 2023

Dec. 15, 2023

Validate user data before passing it to PolyDraw. The program in the bug requests to draw figures outrageously outside the DC's region after presumably, some uninitialized values happen as a result of a missing font. Native gdiplus seems to handle this gracefully so we probably also should. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=41617 Signed-off-by: David Kahurani <k.kahurani(a)gmail.com> -- v5: gdiplus: Clip polygons before drawing them https://gitlab.winehq.org/wine/wine/-/merge_requests/3288

3 5

[PATCH v7 0/4] MR519: vkd3d-shader/dxil: Support minimum precision.
by Conor McCarthy (＠cmccarthy) Dec. 15, 2023

Dec. 15, 2023

-- v7: vkd3d-shader/dxil: Support 16-bit types. vkd3d-shader/spirv: Introduce HALF and UINT16 types for minimum precision. vkd3d-shader/spirv: Introduce a data_type_is_floating_point() helper function. tests/shader-runner: Add tests for minimum-precision constants. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/519

2 4

[PATCH 0/5] MR4702: dmime/tests: Multiple fixes for various Windows test failures.
by Rémi Bernon Dec. 15, 2023

Dec. 15, 2023

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

2 6

[PATCH 0/1] MR4701: kernel32/tests: Fix ProcessMachineTypeInfo tests.
by Hans Leidekker (＠hans) Dec. 15, 2023

Dec. 15, 2023

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

2 1

[PATCH v6 0/5] MR519: vkd3d-shader/dxil: Support minimum precision.
by Conor McCarthy (＠cmccarthy) Dec. 15, 2023

Dec. 15, 2023

-- v6: vkd3d-shader/dxil: Support 16-bit types. vkd3d-shader/spirv: Introduce HALF and UINT16 types for minimum precision. vkd3d-shader/spirv: Introduce a data_type_is_floating_point() helper function. tests/shader-runner: Add tests for minimum-precision constants. tests/shader-runner: Run Shader Model 6 tests in the crossbuild. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/519

3 10

[PATCH v12 0/7] MR443: tests: Add some tests for effects groups syntax.
by Nikolay Sivov (＠nsivov) Dec. 15, 2023

Dec. 15, 2023

Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> -- v12: vkd3d-shader/tpf: Add initial support for writing fx_4_0/fx_4_1 binaries. vkd3d-shader: Add separate binary target type for effects. vkd3d-shader/hlsl: Handle effect group statement. vkd3d-shader/hlsl: Add variables for techniques. vkd3d-shader/hlsl: Rename rule for top-level techniques. vkd3d-shader/hlsl: Add 'fxgroup' token. tests: Add some tests for effects groups syntax. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/443

2 7

Re: [PATCH v3 0/1] MR4694: ntdll: Make sure executable is large address aware and enables dynamic base and high entropy va before free reserved memory
by Looming Linux (＠loominglinux) Dec. 15, 2023

Dec. 15, 2023

Already fixed by 7a7b82880a73e654933b7866e79f3e9a62a565ef! Thanks! Will close this MR! -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4694#note_56056

1 0

Re: [PATCH v3 0/1] MR4694: ntdll: Make sure executable is large address aware and enables dynamic base and high entropy va before free reserved memory - closed
by Looming Linux (＠loominglinux) Dec. 15, 2023

Dec. 15, 2023

This merge request was closed by Looming Linux. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4694

1 0

[PATCH 0/1] MR4700: po: Update Simplified Chinese translation.
by Jactry Zeng (＠jactry) Dec. 15, 2023

Dec. 15, 2023

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

2 1

[PATCH v4 0/3] MR514: tests: Use the vulkan runner to run SM1 compilation tests.
by Francisco Casas (＠fcasas) Dec. 15, 2023

Dec. 15, 2023

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. -- v4: tests: Use the vulkan runner to run SM1 compilation tests. 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

2 4