https://bugs.winehq.org/show_bug.cgi?id=56912
--- Comment #9 from stormtrackertony@gmail.com --- Also, here is the latest response from the software developer. He seems convinced that it's not an issue with his code. I'm looking for some of my old laptops to see if any are non-AVS systems with genuine Windows...
Programmer's repsonse:
"I verified that I chose SSE2 in the compiler options for VS 2022 and 2008, so no AVX instructions should be used. If VS2022 is generating AVX instructions then that's a bug in VS 2022. I doubt that's the case and I don't see vcmpps or cmpps in the asm listing from the compiler. I suspect that the stack in a call is being trashed and the return is jumping into junk, hence the different "instructions" causing the crash on different WINE versions. If there were AVX calls in the 2022 build, I have to believe it would have crashed as soon as the software opened, not waiting until radar data started polling.
In addition, I have looked at the generated code for both VS 2008 and 2022 and found out why 2022 is so much faster. 2008 is not inlining the function and member calls in my code. I don't know why 2008 isn't inlining the member calls properly. 2022 is inlining the calls *and* then optimizing the resulting code. Both compilers are set to "maximize speed", so they're free to generate as much code as needed (e.g. inline generated code) to accomplish the results. "