https://bugs.winehq.org/show_bug.cgi?id=56912
--- Comment #10 from Andrew Nguyen arethusa26@gmail.com --- I tested the GR2Analyst v3 application on AWS EC2 t1.micro instances, which do not have AVX instructions available. I confirmed that AVX instruction capability is unavailable for an instance launched from a Debian 12 AMI, as /proc/cpuinfo reports only the following flags:
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good nopl cpuid tsc_known_freq pni ssse3 cx16 sse4_1 sse4_2 popcnt hypervisor lahf_lm pti
With an instance launched from a Windows Server 2019 Base AMI, I confirmed using CPU-Z that the instruction capabilities reported do not include AVX: MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T.
On the Debian 12 instance, I confirmed for wine-9.0 and wine-9.12 that the application crashes with an illegal instruction exception when performing the reproduction steps. The implicated instruction is the vcmpps instruction as previously noted.
On the Windows Server instance, performing the reproduction steps also results in the application terminating. The event log reported the following details:
Faulting application name: gr2analyst.exe, version: 3.3.0.0, time stamp: 0x667995de Faulting module name: gr2analyst.exe, version: 3.3.0.0, time stamp: 0x667995de Exception code: 0xc000001d Fault offset: 0x0003a534
The exception code corresponds to STATUS_ILLEGAL_INSTRUCTION, so the application probably died in the same way as on Wine.
Therefore, I think the application can unconditionally execute an AVX instruction even on Windows, so there's no evidence of a bug in Wine, and I think this bug should be closed as invalid.