blob: 2bd8fd460e4a2100e9c861fc99e165fb12f5224c (
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
44
45
46
|
x86: 0.995
semantic: 0.974
architecture: 0.868
device: 0.758
other: 0.732
graphic: 0.700
debug: 0.650
performance: 0.552
vnc: 0.544
assembly: 0.531
boot: 0.465
permissions: 0.443
socket: 0.426
network: 0.393
PID: 0.358
register: 0.341
mistranslation: 0.299
risc-v: 0.293
files: 0.280
TCG: 0.255
arm: 0.252
kernel virtual machine: 0.225
x86 SSE/SSE2/SSE3 instruction semantic bugs with NaN
Description of problem
The result of SSE/SSE2/SSE3 instructions with NaN is different from the CPU. From Intel manual Volume 1 Appendix D.4.2.2, they defined the behavior of such instructions with NaN. But I think QEMU did not implement this semantic exactly because the byte result is different.
Steps to reproduce
Compile this code
void main() {
asm("mov rax, 0x000000007fffffff; push rax; mov rax, 0x00000000ffffffff; push rax; movdqu XMM1, [rsp];");
asm("mov rax, 0x2e711de7aa46af1a; push rax; mov rax, 0x7fffffff7fffffff; push rax; movdqu XMM2, [rsp];");
asm("addsubps xmm1, xmm2");
}
Execute and compare the result with the CPU. This problem happens with other SSE/SSE2/SSE3 instructions specified in the manual, Volume 1 Appendix D.4.2.2.
CPU xmm1[3] = 0xffffffff
QEMU xmm1[3] = 0x7fffffff
Additional information
This bug is discovered by research conducted by KAIST SoftSec.
|