https://bugs.kde.org/show_bug.cgi?id=486180
--- Comment #9 from Paul Floyd <pjfl...@wanadoo.fr> --- I really wonder if this is needed on other platforms. Looking at the use prior to the new s390 code, VEX stores the program counter on ppc and x86 but it was only used for Darwin on x86 and amd64. I can't easily check Darwin x86 as the last working version was 10.12 and, well, who cares about x86 Darwin? Apple removed x86 support with 10.15. If the Darwin port ever gets fixed we should probably remove x86 Darwin. amd64 Darwin looks like it only ever intializes the VEX field to 0 but then it uses it in ML_(fixup_guest_state_to_restart_syscall). That might explain a few of the several hundred Darwin regtest failures. All other OSes just subtract the size of the syscall opcode from the program counter. -- You are receiving this mail because: You are watching all bug changes.
