February 2023 - Wine-gitlab

[PATCH v4 0/6] MR2091: windows.media.speech: Initial Unixlib work.
by Bernhard Kölbl 06 Feb '23

06 Feb '23

Second commit is to be removed. Signed-off-by: Bernhard Kölbl <besentv(a)gmail.com> -- v4: windows.media.speech: Implement Vosk create and release functions in the unixlib. windows.media.speech/tests: Allow the SpeechRecognizer creation to fail in Wine. windows.media.speech/tests: Get rid of duplicated hresult. windows.media.speech: Add a unixlib stub. https://gitlab.winehq.org/wine/wine/-/merge_requests/2091

1 6

[PATCH v4 0/1] MR2118: ntdll: Explaining with wine requires a 3G/1G split on 32bit
by Steve Schnepp (＠steveschnepp) 06 Feb '23

06 Feb '23

Windows has a 2G/2G split by default, but some addresses are fixed in the win32 API, so we have to ensure that those addresses are still available in the virtual memory space and not taken by Linux. Kudos to stefand for taking the time to explain on IRC. -- v4: ntdll: Explaining with wine requires a 3G/1G split on 32bit https://gitlab.winehq.org/wine/wine/-/merge_requests/2118

3 7

[PATCH v3 0/4] MR2091: windows.media.speech: Initial Unixlib work.
by Bernhard Kölbl 06 Feb '23

06 Feb '23

Second commit is to be removed. Signed-off-by: Bernhard Kölbl <besentv(a)gmail.com> -- v3: windows.media.speech: Implement Vosk create and release functions in the unixlib. windows.media.speech: Add a unixlib stub. https://gitlab.winehq.org/wine/wine/-/merge_requests/2091

4 35

[PATCH v5 0/2] MR76: vkd3d-shader/hlsl: Support rsqrt() and distance() intrinsics.
by Nikolay Sivov (＠nsivov) 06 Feb '23

06 Feb '23

-- v5: vkd3d-shader/hlsl: Support distance() intrinsic. vkd3d-shader/hlsl: Support rsqrt() intrinsic. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/76

3 3

[PATCH v3 0/1] MR2118: ntdll: Explaining with wine requires a 3G/1G split on 32bit
by Steve Schnepp (＠steveschnepp) 06 Feb '23

06 Feb '23

Windows has a 2G/2G split by default, but some addresses are fixed in the win32 API, so we have to ensure that those addresses are still available in the virtual memory space and not taken by Linux. Kudos to stefand for taking the time to explain on IRC. -- v3: ntdll: Explaining with wine requires a 3G/1G split on 32bit https://gitlab.winehq.org/wine/wine/-/merge_requests/2118

2 2

[PATCH v2 0/1] MR2118: ntdll: Explaining with wine requires a 3G/1G split on 32bit
by Steve Schnepp (＠steveschnepp) 06 Feb '23

06 Feb '23

Windows has a 2G/2G split by default, but some addresses are fixed in the win32 API, so we have to ensure that those addresses are still available in the virtual memory space and not taken by Linux. Kudos to stefand for taking the time to explain on IRC. -- v2: ntdll: Explaining with wine requires a 3G/1G split on 32bit https://gitlab.winehq.org/wine/wine/-/merge_requests/2118

4 4

[PATCH v6 0/1] MR1937: kernelbase: Fix grouping repeat for number formatting.
by Gabriel Ivăncescu 06 Feb '23

06 Feb '23

LOCALE_SGROUPING's string and the `Grouping` field in NUMBERFMTW are confusingly different. The former, which is what is fixed here, treats a '0' as a repeat of the previous grouping. But a 0 at the end of the `Grouping` field prevents it from repeating (it repeats by default otherwise) so it's the opposite. Note that without a '0' in the LOCALE_SGROUPING string, it shouldn't even repeat in the first place. This fixes the typical "3;0" default grouping, for example. See: https://learn.microsoft.com/en-us/windows/win32/intl/locale-sgrouping -- v6: kernelbase: Fix grouping repeat for number formatting. https://gitlab.winehq.org/wine/wine/-/merge_requests/1937

1 3

[PATCH 0/1] MR2118: ntdll: Explaining with wine requires a 3G/1G split on 32bit
by Steve Schnepp (＠steveschnepp) 06 Feb '23

06 Feb '23

Windows has a 2G/2G split by default, but some addresses are fixed in the win32 API, so we have to ensure that those addresses are still available in the virtual memory space and not taken by Linux. Kudos to stefand for taking the time to explain on IRC. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2118

2 1

[PATCH 0/5] MR2098: mshtml: Implement synchronous XMLHttpRequests.
by Gabriel Ivăncescu 06 Feb '23

06 Feb '23

wine-gecko does actually support synchronous XMLHttpRequests, even if they are deprecated, but unfortunately it is very broken compared to IE or all the other major browsers (more details [here](https://bugzilla.mozilla.org/show_bug.cgi?id=697151)) Thankfully, it still provides us with the event message loop, which is enough to fix it on mshtml side and act like IE. For sync XHRs, send() is supposed to block all script code, except for notifications sent to the sync XHR. This is because when send() blocks, no other piece of code in the script should execute other than the sync XHR handlers. Unfortunately, that's not the case in Gecko's broken implementation, which can execute handlers as if they were APCs while it's "blocked" in send(). Note that it doesn't actually block, though, because we still process the message loop (non-event related tasks such as navigation, paints, and other stuff), and that's normal. Gecko doesn't block everything related to script events, only some things on the document and timers, but that's far from enough and not even enough for our purposes since we use our own timer tasks. And not even message events are blocked, even though we *also* use our own message event dispatchers (but it doesn't block Gecko ones either). So what we have to do is we need to track all the timers and events dispatched that result in script handlers being executed, while "blocking" inside of a sync XHR send(), and queue them up to defer them to be dispatched later, after send() unblocks. But this is easier said that done. There are many corner cases to consider here, for example: * Events dispatched *synchronously* from within a sync XHR handler or other piece of code called from it. * Nested sync XHR send() calls (called during handler of another sync XHR). * Async XHRs having their events dispatched during a blocking sync XHR send() are complicated. `readyStateChange` for example needs to have the async XHR's readyState at the time it was sent, **not** at the time it was actually dispatched, since we're going to delay it and dispatch it later. It's similar with other XHR states, such as responseText (which can be partial). * Aborts of async XHRs during such handlers. These patches hopefully should address all the issues and, on a high level, work like this: * Track the `readyState` and `responseText` length manually, so we can override / force them to specific values. * "Snapshot" the async XHR at the time we encounter an event for it, and queue this event with such information. When later dispatching this event (after being deferred), we temporarily set the state of the async XHR to the snapshot. * To deal with nested event dispatches, keep track of a "dispatch depth" (everytime we dispatch an event we increase the depth, and when it returns we decrease it). * For sync XHRs, we note the depth when send() is called, and defer events at that depth, since they're dispatched during the "blocked" message loop and need to be delayed (except for sync XHR events, which is a special case since it must be dispatched synchronously). When it returns, we restore the previous blocking depth. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2098

2 7

[PATCH 0/7] MR2117: More improvements in PDB dumping.
by eric pouech (＠epo) 06 Feb '23

06 Feb '23

This series: - complements PDB dumping in a few areas (internals of MSF, string tables, public stream) - allow to opt in for only a portion of PDB file -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2117

2 7