diff options
Diffstat (limited to 'gitlab/issues/target_i386/host_missing/accel_TCG/1375.toml')
| -rw-r--r-- | gitlab/issues/target_i386/host_missing/accel_TCG/1375.toml | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/gitlab/issues/target_i386/host_missing/accel_TCG/1375.toml b/gitlab/issues/target_i386/host_missing/accel_TCG/1375.toml new file mode 100644 index 00000000..d6d751c4 --- /dev/null +++ b/gitlab/issues/target_i386/host_missing/accel_TCG/1375.toml @@ -0,0 +1,27 @@ +id = 1375 +title = "x86 SSE/SSE2/SSE3 instruction semantic bugs with NaN" +state = "opened" +created_at = "2022-12-16T07:49:50.158Z" +closed_at = "n/a" +labels = ["Softfloat", "accel: TCG", "target: i386", "workflow::Triaged"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/1375" +host-os = "Windows 10 20H2" +host-arch = "x86" +qemu-version = "7.1.90 (v7.2.0-rc0)" +guest-os = "None" +guest-arch = "x86" +description = """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.""" +reproduce = """1. 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"); +} +``` +2. 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 = """This bug is discovered by research conducted by KAIST SoftSec.""" |