https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111969
--- Comment #3 from Patrick O'Neill <patrick at rivosinc dot com> --- These may be real failures that manifest in QEMU depending on the GCC used to compile it. I built qemu with r14-4098-gbdb7d85dde5 which caused the failures. > QEMU_CPU=rv32,vlen=128,v=true,vext_spec=v1.0,Zve32f=true,Zve64f=true > ../build-3/bin/qemu-riscv32 large_2.exe > 0.333333333333333333333333333333333317 > 2.24271998593667819112500193394291495E+1644 > STOP 1 Building again with r14-4875-g9cf2e7441ee, I can execute both the new > QEMU_CPU=rv32,vlen=128,v=true,vext_spec=v1.0,Zve32f=true,Zve64f=true > ./bin/qemu-riscv32 ./large_2.exe _and_ the old exe: > QEMU_CPU=rv32,vlen=128,v=true,vext_spec=v1.0,Zve32f=true,Zve64f=true > ./bin/qemu-riscv32 ../../tc-oct-24-baseline-flaky/build/large_2.exe with no issues/failures. When I run r14-4875-g9cf2e7441ee large_2.exe on r14-4098-gbdb7d85dde5 QEMU, I get the same failure: > QEMU_CPU=rv32,vlen=128,v=true,vext_spec=v1.0,Zve32f=true,Zve64f=true > ../build-3/bin/qemu-riscv32 ../../tc-oct-24-baseline-flaky/build/large_2.exe > 0.333333333333333333333333333333333317 > 2.24271998593667819112500193394291495E+1644 > STOP 1 So it seems to be a QEMU issue that is caused by GCC?
