Non-determinism in test_vm_instr

[ripatel-fd]

GCC and Clang produce different behavior

ripatel@emfr-ossdev-firedancer9: /data/ripatel/firedancer main!
$ build/native/clang/unit-test/test_vm_instr
--log-path ""
No log
WARNING 07-04 15:09:19.575097 1397655 f0   0    src/flamenco/vm/test_vm_instr.c(475): FAIL src/flamenco/vm/instr_test/int_math.instr(292): Expected r0 = 0xf8f3, got 0xf8f9
WARNING 07-04 15:09:19.586623 1397655 f0   0    src/flamenco/vm/test_vm_instr.c(586): fail cnt 1
No log
FAIL

ripatel@emfr-ossdev-firedancer9: /data/ripatel/firedancer main!
$ build/native/gcc/unit-test/test_vm_instr  
--log-path ""
No log
WARNING 07-04 15:09:25.384514 1397701 f0   0    src/flamenco/vm/test_vm_instr.c(475): FAIL src/flamenco/vm/instr_test/int_math.instr(292): Expected r0 = 0xf8f3, got 0xf8f9
WARNING 07-04 15:09:25.384971 1397701 f0   0    src/flamenco/vm/test_vm_instr.c(461): FAIL src/flamenco/vm/instr_test/jump.instr(372): Expected status Fault, got VerifyFail
WARNING 07-04 15:09:25.385520 1397701 f0   0    src/flamenco/vm/test_vm_instr.c(586): fail cnt 1
No log
FAIL