1 files changed, 43 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/118/none/2507 b/results/classifier/zero-shot/118/none/2507
new file mode 100644
index 000000000..15f122043
--- /dev/null
+++ b/results/classifier/zero-shot/118/none/2507
@@ -0,0 +1,43 @@
+device: 0.796
+performance: 0.794
+graphic: 0.730
+ppc: 0.636
+architecture: 0.574
+kernel: 0.524
+network: 0.523
+PID: 0.501
+register: 0.496
+permissions: 0.429
+semantic: 0.414
+VMM: 0.412
+peripherals: 0.408
+vnc: 0.361
+files: 0.342
+debug: 0.341
+i386: 0.325
+boot: 0.320
+arm: 0.310
+risc-v: 0.308
+x86: 0.296
+hypervisor: 0.285
+socket: 0.275
+KVM: 0.269
+TCG: 0.198
+mistranslation: 0.196
+assembly: 0.161
+user-level: 0.097
+virtual: 0.095
+
+m68k: fpu: frestore with NULL state should reset FPU state
+Description of problem:
+According to the PRM:
+
+```
+Floating-Point Status Register: Cleared if the state size is NULL; otherwise, not affected. 
+```
+
+But this does not currently happen.
+Steps to reproduce:
+1. set a value in fpsr
+2. do frestore with state size zero
+3. read back fpsr and notice it isn't zero.