- Wine-GitLab - list.winehq.org

[PATCH 0/1] MR10459: vbscript: Implement DateDiff built-in function.
by Francis De Brabandere (＠francisdb) March 26, 2026

March 26, 2026

Implement DateDiff(interval, date1, date2 [, firstdayofweek [, firstweekofyear]]) with support for all interval types: yyyy, q, m, y, d, w, ww, h, n, s. For yyyy/q/m the difference is computed from calendar fields via VarUdateFromDate. For d/y the day number difference is used. For w it is the day difference integer-divided by 7 (not affected by firstdayofweek). For ww it counts week boundary crossings based on firstdayofweek. For h/n/s the dates are converted to the respective unit and truncated before subtracting. Returns VT_I4 (Long). Null date arguments return Null; null interval or null firstdayofweek/firstweekofyear return VBSE_ILLEGAL_NULL_USE. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10459

2 1

Re: [PATCH v2 0/14] MR10349: opengl32: Implement wglGetProcAddress on the client side.
by Jacek Caban (＠jacek) March 26, 2026

March 26, 2026

On Thu Mar 26 12:51:57 2026 +0000, Rémi Bernon wrote: > Well arguably we have years of testing showing that exposing these > extensions do not break the applications *which are currently working*. > It says nothing about applications that don't work or that weren't > tested. I've recently fixed some compatibility issue caused by passing > through host GL_RENDERER string as is, which broke an application in > some cases, as it was expecting a shorter string than what we returned. > Anyway, I don't mind too much adding support for registered extensions, > although I think we should argue whether it does fix anything, rather > than whether not exposing them breaks something, but I don't think we > should be hardcoding extensions which aren't in the registry. There's no > reason to list Mesa extensions more than other vendors, and we have a > general policy in Wine not to add vendor or backend specific workaround > unless proven necessary, ie: that it *is* native behavior and that doing > it fixes some application. > If ARM Windows uses Mesa for its OpenGL implementation, and if some > application depends on a Mesa specific extension in such situation, we > could *then* consider adding them in such case, but that actually would > need to be done regardless of the host GL implementation because Wine on > ARM isn't always going to run with Mesa. Note that this probably means > that we would be better off with PE Zink in such case anyway, because > otherwise we might end up being simply unable to implement the missing > extension if the host cannot do it for us. Again, it's not about fixing anything. It is about not changing behavior that do not need to be changed in an MR that is already very invasive. We expose it today, and we have no evidence that it is harmful. And again, removing it on top of this MR is trivial and better for bisectability than doing it here. Anyway, I think it is time to agree to disagree. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10349#note_133867

1 0

[PATCH 0/2] MR10458: quartz: Reset the completion event on paused -> running transition.
by Akihiro Sagawa (＠sgwaki) March 26, 2026

March 26, 2026

Otherwise, `WaitForCompletion` method doesn't block and returns immediately after seeking. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10458

2 2

Re: [PATCH v2 0/14] MR10349: opengl32: Implement wglGetProcAddress on the client side.
by Rémi Bernon (＠rbernon) March 26, 2026

March 26, 2026

On Thu Mar 26 11:12:56 2026 +0000, Jacek Caban wrote: > On ARM Windows, OpenGL is implemented on top of Mesa’s D3D12 backend, so > all extensions exposed by Mesa can potentially be present on actual > Windows. Filtering them therefore seems counterproductive, unless we > want to filter based on vendor or something similar, which sounds > brittle and would require a strong justification. > We are currently exposing all of those extensions, and we have years of > testing showing that they do not cause problems (at least for the > applications we already support). As such, exposing them should not > introduce regressions. The intention behind adding those entries is to > limit the impact of the patch that tokenizes extensions. Hypothetically, > if we do have a reason to filter any of them after all, I think it would > be better to remove them from make_opengl in a separate change, so that > a potential bisect clearly points to the filtering change rather than to > a commit whose primary purpose is tokenization. That said, even for > extensions currently not exposed by Windows drivers, I believe filtering > would be counterproductive and not forward-compatible by definition, as > future Windows drivers may start exposing them at any time. > Perhaps we should consider adding even more of them to make_opengl. I > initially added the ones observed on my drivers, which seemed like a > reasonable compromise. Well arguably we have years of testing showing that exposing these extensions do not break the applications *which are currently working*. It says nothing about applications that don't work or that weren't tested. I've recently fixed some compatibility issue caused by passing through host GL_RENDERER string as is, which broke an application in some cases, as it was expecting a shorter string than what we returned. Anyway, I don't mind too much adding support for registered extensions, although I think we should argue whether it does fix anything, rather than whether not exposing them breaks something, but I don't think we should be hardcoding extensions which aren't in the registry. There's no reason to list Mesa extensions more than other vendors, and we have a general policy in Wine not to add vendor or backend specific workaround unless proven necessary, ie: that it *is* native behavior and that doing it fixes some application. If ARM Windows uses Mesa for its OpenGL implementation, and if some application depends on a Mesa specific extension in such situation, we could *then* consider adding them in such case, but that actually would need to be done regardless of the host GL implementation because Wine on ARM isn't always going to run with Mesa. Note that this probably means that we would be better off with PE Zink in such case anyway, because otherwise we might end up being simply unable to implement the missing extension if the host cannot do it for us. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10349#note_133862

1 0

[PATCH v2 0/2] MR10451: comctl32/treeview: Implemented TVN_ITEMCHANGING
by Piotr Pawłowski (＠DEATH) March 26, 2026

March 26, 2026

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=59456 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55707 -- v2: comctl32/treeview: Implemented TVN_ITEMCHANGING & TVN_ITEMCHANGED comctl32/tests: Enabled test_select() for comctl32 v6, made test for TVN_ITEMCHANGING & TVN_ITEMCHANGED https://gitlab.winehq.org/wine/wine/-/merge_requests/10451

2 2

[PATCH 0/5] MR10163: server: Create the new process first thread in new_process request.
by Rémi Bernon March 26, 2026

March 26, 2026

In preparation for doing something like https://gitlab.winehq.org/wine/wine/-/merge_requests/10058, this also saves one wineserver request on process creation by creating the first thread in new_process. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10163

3 8

Re: [PATCH v2 0/14] MR10349: opengl32: Implement wglGetProcAddress on the client side.
by Jacek Caban (＠jacek) March 26, 2026

March 26, 2026

> GLSL extensions aren't supposed to be exposed there, unless they have a matching GL extension to add tokens / commands or change GL behavior. This one doesn't do any of that on the GL side, and I believe it is not meant to be exposed in GL_EXTENSIONS. Well, it's exposed by Mesa's `GL_EXTENSIONS`. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10349#note_133858

1 0

Re: [PATCH v2 0/14] MR10349: opengl32: Implement wglGetProcAddress on the client side.
by Jacek Caban (＠jacek) March 26, 2026

March 26, 2026

On Tue Mar 24 13:37:32 2026 +0000, Rémi Bernon wrote: > The issue I see is that exposing extensions that aren't expected to be > there by applications have a chance of confusing them. It's possible for > instance that an application check for GL_ANGLE extension and decide to > enable some ANGLE specific rendering mode. On Windows the AMD drivers do > not support those extensions, but on Wine most of the time Mesa is used > for AMD GPUs and they would be exposed. > The same logic applies to platform specific extensions like GL_APPLE or > other platform extensions that are currently filtered out. Sure > `make_opengl` could support some of them, and sure, GL extensions aren't > restricted and some other driver could implement them including on > Windows, but it's not the case in practice and passing them through > creates a runtime environment that differ from any possible native > environment Windows applications have been developed for. > Filtering out extensions which aren't, or very rarely, there on Windows > is less likely to break anything, because no application is expected to > benefit from them anyway. On ARM Windows, OpenGL is implemented on top of Mesa’s D3D12 backend, so all extensions exposed by Mesa can potentially be present on actual Windows. Filtering them therefore seems counterproductive, unless we want to filter based on vendor or something similar, which sounds brittle and would require a strong justification. We are currently exposing all of those extensions, and we have years of testing showing that they do not cause problems (at least for the applications we already support). As such, exposing them should not introduce regressions. The intention behind adding those entries is to limit the impact of the patch that tokenizes extensions. Hypothetically, if we do have a reason to filter any of them after all, I think it would be better to remove them from make_opengl in a separate change, so that a potential bisect clearly points to the filtering change rather than to a commit whose primary purpose is tokenization. That said, even for extensions currently not exposed by Windows drivers, I believe filtering would be counterproductive and not forward-compatible by definition, as future Windows drivers may start exposing them at any time. Perhaps we should consider adding even more of them to make_opengl. I initially added the ones observed on my drivers, which seemed like a reasonable compromise. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10349#note_133857

1 0

[PATCH 0/1] MR10424: services: Cancel overlapped IO after timeout.
by Yuxuan Shui (＠yshui) March 26, 2026

March 26, 2026

Though WaitForSingleObject timed out, the IO operation is still running in the background. After the function process_send_command returns, the OVERLAPPED object referenced by this IO operation becomes invalid. Later, when this IO finally completes, server_select will use invalid stack memory. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10424

4 8

[PATCH 0/1] MR10456: vbscript: Implement DatePart built-in function.
by Francis De Brabandere (＠francisdb) March 26, 2026

March 26, 2026

Implement DatePart(interval, date [, firstdayofweek [, firstweekofyear]]) with support for all interval types: yyyy, q, m, y, d, w, ww, h, n, s. The week-of-year ("ww") calculation handles all three firstweekofyear modes (vbFirstJan1, vbFirstFourDays, vbFirstFullWeek) including the edge case where dates before week 1 belong to the last week of the previous year. Uses VarUdateFromDate for day-of-year information. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10456

2 1