--
v4: tests: Add a test for fmod() with vector arguments.
vkd3d-shader: Use ternary operator in fmod() implementation.
vkd3d-shader/tpf: Use 'movc' to implement ternary operator.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/268
Win10 introduced the ability for OutputDebugStringW to send
Unicode strings (instead of translating the Unicode string
to ANSI and call OutputDebugStringA).
This series:
- add a couple of tests for covering various aspects
+ how exception with unicode string is constructed,
+ interaction with WaitForDebugEvent and
WaitForDebugEventEx
- implements WaitForDebugEventEx()
- emit unicode string from OutputDebugStringW
- introduce manifest constants to describe stages in
exception testing (this let adding new stages way
easier). Note this has not been tested on ARM.
The tests results are not fully green because of existing issues
in ntdll:exception (see https://bugs.winehq.org/show_bug.cgi?id=55111
for win8 and early win10, and all the failing ones in Win11...).
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3596
On Wed Aug 16 21:48:02 2023 +0000, Bartosz Kosiorek wrote:
> How it could be done (set \*result when you return)?
I just mean set *result before you return, just like you do about 5 lines before.
It appears 0 would the appropriate value, in which case you could combine the if blocks.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3581#note_42603
Jeffrey Smith (@whydoubt) commented about dlls/gdiplus/tests/pathiterator.c:
> GpPath *path;
> GpPathIterator *iter;
> GpStatus stat;
> - INT start, end, result;
> - BOOL closed;
> + INT start, end, result, closed;
I would leave the type as BOOL, to make it match the 4th parameter of GdipPathIterNextSubpath.
But since it is implemented as an integer (as opposed to an actual boolean that only accepts true/false), it can contain any value that an INT can, so the tests should still be fine.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3581#note_42601
I stumbled onto this while using freopen() for debugging purposes.
Basically, freopen() fails if the FILE has been created with
an invalid handle.
So, this MR contains:
- basic tests for freopen (no issue there, just for coverage purposes)
- tests for freopen on FILE with invalid handle
- fix for freopen
--
v3: msvcrt: Fix freopen() on FILE with invalid underlying fd.
msvcrt/tests: Add tests for freopen().
https://gitlab.winehq.org/wine/wine/-/merge_requests/3578