- Wine-gitlab - list.winehq.org

Re: [PATCH v4 0/1] MR730: user32: Implement DefRawInputProc. - approved
by Alexandre Julliard (＠julliard) 01 Sep '22

01 Sep '22

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

1 0

Re: [PATCH v3 0/5] MR755: uxtheme: Do not draw parent background even if scrollbar arrows and thumb are transparent. - approved
by Alexandre Julliard (＠julliard) 01 Sep '22

01 Sep '22

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

1 0

Re: [PATCH v2 0/1] MR757: dwrite: Handle variation selectors 17-256 in MapCharacters(). - approved
by Alexandre Julliard (＠julliard) 01 Sep '22

01 Sep '22

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

1 0

[PATCH 0/1] MR766: advapi32/test: Add tests for RegLoadAppKey.
by Santino Mazza (＠tati1454) 01 Sep '22

01 Sep '22

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

3 2

[PATCH v2 0/5] MR731: mshtml: Implement props forwarding for Storage.
by Gabriel Ivăncescu 01 Sep '22

01 Sep '22

This implements props access to the underlying items in the storage, which is supported on native (although quirky). Unlike most normal props, the underlying storage for the props is asynchronous, so it can disappear or appear at any point, so they have to be re-checked as needed. The props themselves just map a name to a DISPID, but other than that, DISP_E_MEMBERNOTFOUND can return even after a successful GetDispID for example, even if GetDispID already checked for the item (which it has to, for e.g. (x in y) check). It also contains some fixes for enumerating props, which are needed now because these props also have to be enumerated. They are custom props, so it's needed to have GetMemberName work for them. And since they are asynchronous it makes it even more complicated when enumerating. -- v2: mshtml: Implement props enumeration for Storage. mshtml: Implement GetMemberName for custom props. mshtml: Do not enumerate hidden builtin props. mshtml: Implement deleting props for Storage. mshtml: Implement props for Storage by forwarding to the underlying storage. https://gitlab.winehq.org/wine/wine/-/merge_requests/731

3 8

[PATCH v2 0/1] MR752: winecrt0: run C++ object destructors in DLL_PROCESS_DETACH.
by Kevin Puetz (＠puetzk) 01 Sep '22

01 Sep '22

Run C++ global/static destructors during DLL_PROCESS_DETACH while other other dllimport functions they may want to call are still viable. While windows imposes many restrictions on what may be done in such destructors (given that the run inside the loader lock), there are lots of legal and useful kernel32 functions like DestroyCriticalSection, DeleteAtom, TlsFree, etc that are both useful and legal. Currently this does not work for builtin modules because all the Win32 structures are discarded well before NtUnmapViewOfSection finally does the dlllose. Even for a winelib .dll.so module, it would be preferable for destructors to execute during process_detach (before wine tears down the MODREF and detaches dependant dlls), rather than be left until after the last NtUnmapViewOfSection (when we finally reach dlclose) Therefore, winegcc now always uses the DllMainCRTStartup entry point unless you specify your own --entry=func. Previously it did this only for PE modules using msvcrt. Making this default consistent matches cl.exe, which also always defaults to _DllMainCRTStartup unless overridden by /entry:foo https://docs.microsoft.com/en-us/cpp/build/reference/entry-entry-point-symb… The ELF version of winecrt0.a now provides a DllMainCRTStartup which, per the Itanium ABI that is in practice what is used by gcc and clang, performs this this destruction by calling __cxa_finalize(&__dso_handle).. This libc function is required to be idempotent, so it's OK that dlclose still calls it again later (there will just be no further work to do). Multiple calls to __cxa_finalize shall not result in calling termination function entries multiple times; the implementation may either remove entries or mark them finished. https://itanium-cxx-abi.github.io/cxx-abi/abi.html#dso-dtor-runtime-api This has two main effects; it moves ELF destructors earlier (before imports are unmapped), and it moves them inside the Nt loader lock. Being earlier was the intended goal, and moving them inside the lock seems fine. Any Win32 API calls in destructors are just being subjected to the same lock hierarchy rules as usual on windows (MSVC also runs destructors from DllMainCrtStartup) https://docs.microsoft.com/en-us/cpp/build/run-time-library-behavior?view=m… And any purely-ELF destructors that happen to also run earlier should never call functions exported from wine (and thus don't care about ntdll's locks). -- v2: winecrt0: run C++ object destructors in DLL_PROCESS_DETACH. https://gitlab.winehq.org/wine/wine/-/merge_requests/752

2 4

[PATCH v3 0/5] MR729: windows.media.speech: Initial recognition session work.
by Bernhard Kölbl 01 Sep '22

01 Sep '22

-- v3: windows.media.speech: Implement a worker thread for the recognition session. https://gitlab.winehq.org/wine/wine/-/merge_requests/729

2 7

[PATCH v7 0/8] MR717: Implement application hives in the registry
by Santino Mazza (＠tati1454) 01 Sep '22

01 Sep '22

Initial implementation for registry application hives, this is a step forward to get Visual Studio to run. :-) -- v7: server: save app hive into it's file when closing handle. server/registry: pass file name instead of file handle to server. kernelbase: Implement RegLoadAppKey. ntdll: Initial implementation for application hives. ntdll: Move NtLoadKey implementation to NtLoadKeyEx. https://gitlab.winehq.org/wine/wine/-/merge_requests/717

3 12

[PATCH 0/2] MR762: winevulkan: Update to VK spec version 1.3.226.
by Georg Lehmann (＠DadSchoorse) 01 Sep '22

01 Sep '22

Not trivial this time because VK_NV_mesh_shader now aliases 64bit enum values that are only later defined by VK_EXT_mesh_shader. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/762

2 2

[PATCH 0/3] MR758: d3d10: Test D3D10CreateEffectFromMemory.
by Ziqing Hui (＠zhui) 01 Sep '22

01 Sep '22

The test results show that data passed to D3D10CreateEffectFromMemory won't be modified. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/758

4 7