https://bugs.winehq.org/show_bug.cgi?id=47198
--- Comment #114 from David Torok dt@zeroitlab.com --- (In reply to Zebediah Figura from comment #113)
(In reply to neyl from comment #112)
With Wine 7.1 released we now have a lot of PE modules and WoW64 thunks. What is missing to get this bug properly fixed?
Without changing the %cs segment, we still need:
- the ability to change %gs in the wine syscall thunk, which we can only
safely do once all modules have been converted to PE. I'm going to go ahead and repurpose/narrow this bug report for this specific issue;
- the ability to execute 64-bit syscalls in a 32-bit process, which we can
only safely do once all modules have WoW64 thunks written and the last parts of WoW64 support are in place. I've split this off into bug 52483;
- the ability to catch direct x86_64 SYSCALL instructions (bug 48291).
Well, this was a while back but as I remember I don't believe syscalls were executed after the far jump that changes %cs. Between the 2 far jump %cs changes only the 64 bit TEB->PEB access happened. So as far as I understand, there is no need to be able to "directly execute" 64 bit syscalls from a 32 bit process. The normal "syscall path" for this application follows wine's own syscall thunks. (Therefore also eliminating the need to solve bug 48291)
The only one left I think is changing %gs.