- 10 Nov, 2021 26 commits
-
-
Rémi Bernon authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51922Signed-off-by:
Rémi Bernon <rbernon@codeweavers.com> Signed-off-by:
Alexandre Julliard <julliard@winehq.org>
-
Rémi Bernon authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51922Signed-off-by:
-
Rémi Bernon authored
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51922Signed-off-by:
-
Rémi Bernon authored
Signed-off-by:
-
Rémi Bernon authored
Using a notification event to wait for input, addressing spurious failures or timeouts. Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
Zebediah Figura <zfigura@codeweavers.com> Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
Jacek Caban <jacek@codeweavers.com> Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com> Signed-off-by:
-
Nikolay Sivov authored
Signed-off-by:
-
Jacek Caban authored
Signed-off-by:
-
Gabriel Ivăncescu authored
We let gecko parse a dummy unknown tag (after validation) using a contextual fragment, and then copy its attributes to the proper element with correct tag. Signed-off-by:
Gabriel Ivăncescu <gabrielopcode@gmail.com> Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
Henri Verbeet <hverbeet@codeweavers.com> Signed-off-by:
-
Zebediah Figura authored
That is, no longer allocate a wined3d_bo_gl as part of the wined3d_buffer_gl structure. Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Zebediah Figura authored
Signed-off-by:
-
Henri Verbeet authored
Rémi Bernon reports an unspecified issue with gcc 11 related to compute_sphere_visibility() expecting 12 input planes, but d3d_device3_ComputeSphereVisibility() only providing 6. The actual number of planes required depends on the "enabled_planes" mask. This patch should make the code better reflect that, but I do not have a gcc 11 setup to verify it resolves the issue there. Signed-off-by:
-
Alistair Leslie-Hughes authored
Native msado15 queries this to workout if interface IMultipleResults can be used with CreateCommand. Signed-off-by:
Alistair Leslie-Hughes <leslie_alistair@hotmail.com> Signed-off-by:
-
Bernhard Kölbl authored
Prevent division by zero exceptions from being thrown, if they are enabled and calls to xmlXPathInit() are being made. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52003Signed-off-by:
Bernhard Kölbl <besentv@gmail.com> Signed-off-by:
-
Alexandre Julliard authored
Signed-off-by: -
Alexandre Julliard authored
Signed-off-by: -
Aurimas Fišeras authored
Signed-off-by:
Aurimas Fišeras <aurimas@members.fsf.org> Signed-off-by:
-
Floris Renaud authored
Signed-off-by:
Floris Renaud <jkfloris@dds.nl> Signed-off-by:
-
- 09 Nov, 2021 14 commits
-
-
Martin Storsjö authored
This matches what was done for x86_64 in 882980c1. Signed-off-by:
Martin Storsjö <martin@martin.st> Signed-off-by:
-
Martin Storsjö authored
Signed-off-by:
-
Martin Storsjö authored
Signed-off-by:
-
Martin Storsjö authored
This is a very close copy of the arm64 implementation. Signed-off-by:
-
Martin Storsjö authored
Store the original stack pointer (on entry to the syscall dispatcher) in syscall_frame; the stack pointer itself is incremented by "pop {r0-r3}" right before calling the syscall itself. This fixes unwinding from functions set up by syscalls, like KiUserExceptionDispatcher. Signed-off-by: -
Martin Storsjö authored
We ideally should back up all of d0-d31, but when building in ELF form, only d0-d15 are normally available (with common distributions' default compilers), unless object files are built with flags to enable support for d16-d31 (with e.g. -mfpu=neon). Signed-off-by:
-
Martin Storsjö authored
RtlCaptureContext doesn't set context->Lr, which is needed for being able to unwind from the context. This matches what is done in the arm64 version. Signed-off-by:
-
Martin Storsjö authored
This does the same as 23b44e8d, but for arm: Don't call KiUserExceptionDispatcher directly on the stack pointer stored in the CONTEXT, but use the one stored in syscall_frame (which includes the stack allocation in e.g. RtlRaiseException). Signed-off-by:
-
Martin Storsjö authored
This differs slightly from the official docs (which is clear in some places, vague in others, and contradictory in some places), based on actual observed behaviour. Signed-off-by:
-
Martin Storsjö authored
This isn't mentioned in the documentation (which only writes out the instruction that is executed while unwinding, i.e. the mirror form of it), but a prologue version of this instruction would look like this. Signed-off-by:
-
Martin Storsjö authored
Signed-off-by:
-
Martin Storsjö authored
Signed-off-by:
-
Martin Storsjö authored
Signed-off-by:
-
Martin Storsjö authored
Signed-off-by:
-
