Martin Storsjö 4934c12762 wow64: Use the right SEH opcode in raise_exception on arm64. ... On ARM and ARM64, each SEH opcode is supposed to map to exactly one instruction; the operation of writing x29+x30 with a stack offset with writeback is called ".seh_save_fplr_x". Using the right opcode would fix inconsistent unwinding if we would unwind from near the end of the prologue (which is implausible here). However, clang/LLVM might also get checking for mismatches between SEH opcodes and the prolog/epilog ranges (https://reviews.llvm.org/D131394), mainly to guard against inconsistencies in the unwind info generated by the compiler, but that would trigger on this handwritten function too.		2022-10-10 11:01:32 +02:00
..
file.c
Makefile.in
process.c	wow64: Use the right SEH opcode in raise_exception on arm64.	2022-10-10 11:01:32 +02:00
registry.c	ntdll: Create NtLoadKeyEx syscall stub.	2022-09-09 23:21:58 +02:00
security.c
struct32.h
sync.c
syscall.c	wow64: Don't re-enter cpu_simulate() from exception filter.	2022-09-08 18:42:48 +02:00
syscall.h	ntdll: Create NtLoadKeyEx syscall stub.	2022-09-09 23:21:58 +02:00
system.c
virtual.c	wow64: Return error from NtQueryVirtualMemory(MemoryBasicInformation) for a too-large address.	2022-07-26 22:37:48 +02:00
wow64.spec
wow64_private.h	wow64: Return error from NtQueryVirtualMemory(MemoryBasicInformation) for a too-large address.	2022-07-26 22:37:48 +02:00