January 2026 - Wine-GitLab - list.winehq.org

[PATCH v22 0/17] MR7111: support building Wine with LTO
by Konstantin Demin (＠rockdrilla) Jan. 14, 2026

Jan. 14, 2026

relevant bug reports: - https://bugs.winehq.org/show_bug.cgi?id=41712 - https://bugs.winehq.org/show_bug.cgi?id=51051 -- v22: ntoskrnl: move i386 specific Rtl*ByteSwap() into separate source. ntoskrnl: move _chkstk() / __chkstk() into separate source. msvcrt: move i386 specific _ftol() into separate source. kernel32: move x86-64 specific GetProcAddress() into separate source. kernel32: move i386 specific Interlocked*() into separate source. kernel32: move i386 specific ExitProcess() into separate source. kernelbase: move x86-64 specific GetProcAddress() into separate source. ntdll: move i386 specific Rtl*ByteSwap() into separate source. tools: add LTO quirks. makedep: support skipping/disabling LTO. configure: enable building Wine with LTO. makedep: support LTO builds. winegcc: support LTO builds. winebuild: support LTO builds. tools: helper functions for LTO builds. ntdll: add attribute "used" to a few symbols that should not be discarded. loader: add attribute "used" to a few symbols that should not be discarded. This merge request has too many patches to be relayed via email. Please visit the URL below to see the contents of the merge request. https://gitlab.winehq.org/wine/wine/-/merge_requests/7111

1 0

[PATCH 0/2] MR9886: winebus: Use smallest report size for joystick axis
by Rémi Bernon Jan. 14, 2026

Jan. 14, 2026

Supersedes https://gitlab.winehq.org/wine/wine/-/merge_requests/9789 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9886

2 3

[PATCH v3 0/2] MR9875: Implement InterruptTimeBias and use it in RtlQueryUnbiasedInterruptTime.
by Marc-Aurel Zent (＠mzent) Jan. 14, 2026

Jan. 14, 2026

After https://gitlab.winehq.org/wine/wine/-/merge_requests/8916 `RtlQueryUnbiasedInterruptTime` now includes suspend time as well when it shouldn't. This fixes this and also allows other components like winevulkan to ~~use `RtlQueryUnbiasedInterruptTime`, if that kind of tick count is necessary there~~ get the InterruptTimeBias for their own clock conversions. ~~Since calculating the bias is relatively expensive, this is done together with the timezone bias update every second in such a way that it can only monotonically increase.~~ -- v3: server: Calculate and store InterruptTimeBias in user shared data. ntdll: Subtract InterruptTimeBias in RtlQueryUnbiasedInterruptTime(). https://gitlab.winehq.org/wine/wine/-/merge_requests/9875

3 6

[PATCH 0/8] MR9885: msado15: Performance and initialization improvements.
by Piotr Caban (＠piotr) Jan. 14, 2026

Jan. 14, 2026

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

2 8

[PATCH v2 0/1] MR9882: kernelbase: Trim whitespaces from the quoted 'cmdline'
by Yeshun Ye (＠yeyeshun) Jan. 14, 2026

Jan. 14, 2026

If 'name' does not have a suffix, a suffix will be appended in find_exe_file. If 'name' contains spaces, it will result in an incorrect filename being concatenated. In the log of a certain installer, I saw an entry like this: trace:process:CreateProcessInternalW app (null) cmdline L"\"C:\\Program Files\\some folder\\7za \" x -y -aos \"-oC://Program Files//target folder/\" \"C://Program Files//source.zip\"" Signed-off-by: YeshunYe <yeyeshun(a)uniontech.com> -- v2: kernelbase: Trim whitespaces from the quoted 'cmdline' https://gitlab.winehq.org/wine/wine/-/merge_requests/9882

3 3

[PATCH 0/3] MR9867: vcruntime140_1, msvcp140*: DLL version bumps
by Tim Clem (＠tclem) Jan. 14, 2026

Jan. 14, 2026

14.50 is out now, and at least one game has started looking for 14.44 (The Last Caretaker). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9867

3 6

[PATCH 0/2] MR9853: Draft: winebus: Add support for `EV_BTN` to udev
by Tomasz Pakuła Jan. 14, 2026

Jan. 14, 2026

Adds support for new EV_BTN event that'll be used in place of EV_KEY for joysticks and maybe gamepads. This event doesn't require any mapping as it simply passes through button number as the code (starting from 1 just like HID) and it's value. It was needed to cleanly support joysticks and simracing/simflight hardware that defines more than 80 buttons. Some HW used hacks in the drivers that assigned random usages found lower then TRIGGER_HAPPPY range. WIP work dependent on upstream patches to LKML which I'll link later. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9853

2 7

[PATCH v3 0/3] MR7429: winex11: Support absolute rawinput events and use window-relative coordinates.
by Rémi Bernon Jan. 14, 2026

Jan. 14, 2026

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51357 Now that we're tracking window position changes as they arrive, they should always be consistent with the received mouse input events. Absolute rawinput is useful for tablets, touchpad or touchscreen when they are exposed as absolute mouse devices. -- v3: winex11: Use window-relative coordinates for mouse input. winex11: Add support for absolute position in RawMotion events. winex11: Clear the MOUSEEVENTF_MOVE flag when accumulating motion. https://gitlab.winehq.org/wine/wine/-/merge_requests/7429

3 6

[PATCH 0/1] MR8452: Draft: gitlab: Set WINEPREFIX to a job workspace sub-directory.
by Rémi Bernon Jan. 14, 2026

Jan. 14, 2026

Although I have trouble reproducing it I still experience weird test failures whenever I create or updated separate MRs in a short amount of time. These failures are usually coming from unexpected display settings, although each job is running within docker in an isolated environment. I don't have any explanation for this, and I have confirmed that separate X server are spawned. However, the prefix used for the tests is initialized to /home/gitlab/.wine and I suspect this could perhaps be mounted and shared across containers? It could also explain the failures, if, for instance wineserver starts while another instance (invisible as isolated in a separate container) is running and has updated the registry on disk with different display settings while the tests are being executed. This is hypothetical but nonetheless I think it's better to keep the prefix in a job workspace sub-directory. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8452

3 6

[PATCH v2 0/4] MR9510: Draft: win32u: Implement timeline semaphore rewinding.
by Rémi Bernon Jan. 14, 2026

Jan. 14, 2026

Pretty much the same kind of thing Proton does, this is only for non-shared semaphores for now. This creates timeline events backed by host timeline semaphores, for every wait and signal operation on a client timeline semaphore. Events are host timeline semaphores with monotonically increasing values. One event is a `(host semaphore, value)` unique tuple, and their value is incremented every time they get signaled. They can be reused right away as a different event, with the new value. Signaled events are queued to a per-device event list for reuse, as we cannot safely destroy them [^1] and as creating them might be costly. A thread is spawned for every device that uses timeline semaphores, monitoring the events and semaphore value changes. The semaphore wrapper keeps the current client semaphore value, which is read directly by `vkGetSemaphoreCounterValue`. CPU and GPU waits on the client semaphore are swapped with a wait on a timeline event, and GPU signals with a signal on a timeline event. CPU signals simply update the client semaphore value on the wrapper, signaling the timeline thread to check and notify any waiter. The timeline thread waits on signal events, coming from the GPU, and on a per-device semaphore for CPU notifications (wait/signal list updates, CPU-side signal). It will then signal any pending wait for a client semaphore value that has been reached, and removes timed out waits. --- For shared semaphores my idea is to use the client timeline semaphore host handle itself as a signal to notify other device threads of semaphore value changes, as the host semaphore is what is exported and imported in other devices. The timeline threads would wait on that semaphore too in addition to the signal events and thread notification semaphore. The main issue with shared semaphores actually comes from sharing the client semaphore values, so that they can be read from each device timeline threads as well as from other processes. There's two scenarios to support, one that is for in-process sharing which could perhaps keep the information locally, but we also need to support cross-process sharing so I think there's no other way than to involve wineserver. My idea then is to move shared semaphore client value to wineserver, which will cost a request on every signal and wait (and reading the value for waits could later be moved to a shared memory object). This will also allow us to implement `D3DKMTWaitForSynchronizationObjectFromCpu` which might be useful for D3D12 fence implementation as it'll allow us to translate a timeline semaphore wait to an asynchronous NT event signal. [^1]: Vulkan spec indicates that semaphores may only be destroyed *after* every operation that uses them has fully executed, and it's unclear whether signaling or waiting a semaphore is enough as an indicator for full execution or whether we would need to wait on a submit fence. -- v2: win32u: Implement timeline semaphore rewinding support. win32u: Make a copy of the timeline semaphore value arrays. win32u: Spawn a device thread for timeline semaphores. win32u: Hook more vulkan timeline semaphore functions. https://gitlab.winehq.org/wine/wine/-/merge_requests/9510

3 9