summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/none/2507
blob: 15f122043e83637f6238d9b82cba7406e74fcfc4 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
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.