summary refs log tree commit diff stats
path: root/classification/semantic_issues/gitlab_semantic_addsubps
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-03 14:41:43 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-06-03 14:41:43 +0200
commitd760c82f4244dc47f5413c3c88b640bb1f0f2d9e (patch)
treeba963e9c548a5f19da2665005ce85946c601cd36 /classification/semantic_issues/gitlab_semantic_addsubps
parent256709d2eb3fd80d768a99964be5caa61effa2a0 (diff)
downloadqemu-analysis-d760c82f4244dc47f5413c3c88b640bb1f0f2d9e.tar.gz
qemu-analysis-d760c82f4244dc47f5413c3c88b640bb1f0f2d9e.zip
move semantic_issues dir to results
Diffstat (limited to 'classification/semantic_issues/gitlab_semantic_addsubps')
-rw-r--r--classification/semantic_issues/gitlab_semantic_addsubps23
1 files changed, 0 insertions, 23 deletions
diff --git a/classification/semantic_issues/gitlab_semantic_addsubps b/classification/semantic_issues/gitlab_semantic_addsubps
deleted file mode 100644
index 60438ff08..000000000
--- a/classification/semantic_issues/gitlab_semantic_addsubps
+++ /dev/null
@@ -1,23 +0,0 @@
-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.