http://bugs.winehq.org/show_bug.cgi?id=58335
--- Comment #80 from Bernhard Übelacker bernhardu@mailbox.org --- (In reply to Dmitry Timoshkov from comment #79)
(In reply to Michael Setzer II from comment #77)
Created attachment 78890 [details] out 7
This log doesn't contain execution of avx_sample.exe, and there's no crash in it.
Hello Dimitry, that was for my request.
It shows in __wine_syscall_dispatcher:
=> 0x7ffff7cfed8c <__wine_syscall_dispatcher+208>: xsave64 0xc0(%rcx) 2: /x $xmm6.v2_int64 = {0x7ffffe324e90, 0x7ffffe325a10} 4: /x $rcx = 0x7ffffe0ffd00
=> 0x7ffff7cfee83 <__wine_syscall_dispatcher+455>: movaps 0x1c0(%rcx),%xmm6 2: /x $xmm6.v2_int64 = {0x7ffffe324e90, 0x7ffffe325a10} # after execution: 2: /x $xmm6.v2_int64 = {0x0, 0x0} 4: /x $rcx = 0x7ffffe0ffd00
In my non-avx VM I just reach the fxsave64 path, which writes at offset 256 the register xmm6 to the stack. ( https://www.felixcloutier.com/x86/fxsave )
In Michaels failing machine we reach a instruction xsave64, but I could not yet find if that is supposed to save xmm6 register?