https://bugs.winehq.org/show_bug.cgi?id=56912
--- Comment #6 from Zeb Figura z.figura12@gmail.com --- (In reply to stormtrackertony from comment #5)
(In reply to Zeb Figura from comment #4)
It works here, but that's on a machine with AVX support. I'm not sure if I have a machine old enough to not support AVX...
Thank you for your help with this. When you say "it works here", do you mean on an actual Windows operating system with AVX support or with WINE on a computer with AVX support?
On Wine.
Just to make sure the problem is clear: The original install of the software (first link posted on my last reply) will load the radar data on actual Windows and on WINE....The new, updated version (second link from my last post) still loads radar data on actual Windows but throws an error on WINE (the map still displays on WINE, but it crashes when I click that button under the "file" tab to get the radar data).
Right, I did install the update. Hopefully I did it correctly.
My goal is to get that new version working with WINE. The software developer seems to think it's a bug in WINE since it works normally with actual Windows and he doesn't see anything in his code that would cause the error I'm getting in my WINE backtrace. He also said the only requirement is DirectX 11 and that it should work fine even on old systems (as far back as Windows Vista)
The program tries to execute an AVX instruction, and that's generating SIGILL. That implies the target processor doesn't support AVX (this can be easily confirmed by looking for the presence of "avx" in the "flags" line of /proc/cpuinfo).
The simplest theory is that the program (or bundled libraries) does depend on AVX. It's kind of easy to miss this since AVX is relatively old (2011 IIRC?) In order to test this one would need a Windows install on a processor that doesn't support AVX. I'm not sure I have access to such a machine.
Likely the default compilation flags and/or redists changed between Visual Studio 2008 and 2022.
It's also possible that the program is able to handle a lack of AVX, but is incorrectly detecting that Wine supports AVX. I find this a little unlikely—I think Wine's feature detection is in good shape—but it's possible.