summary refs log tree commit diff stats
path: root/results/classifier/semantic-bugs/instruction/1095857
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-12 09:56:59 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-06-12 09:56:59 +0200
commitb89a938452613061c0f1f23e710281cf5c83cb29 (patch)
treed5faecfd167e088848cad894f8dc9cfef3352e3b /results/classifier/semantic-bugs/instruction/1095857
parent7b681b9f9eedaad2f081ae11a32f459f5a1312ff (diff)
downloadqemu-analysis-b89a938452613061c0f1f23e710281cf5c83cb29.tar.gz
qemu-analysis-b89a938452613061c0f1f23e710281cf5c83cb29.zip
add manually reviewed semantic bugs
Diffstat (limited to 'results/classifier/semantic-bugs/instruction/1095857')
-rw-r--r--results/classifier/semantic-bugs/instruction/109585729
1 files changed, 29 insertions, 0 deletions
diff --git a/results/classifier/semantic-bugs/instruction/1095857 b/results/classifier/semantic-bugs/instruction/1095857
new file mode 100644
index 000000000..a74648b9b
--- /dev/null
+++ b/results/classifier/semantic-bugs/instruction/1095857
@@ -0,0 +1,29 @@
+instruction: 0.914
+mistranslation: 0.764
+graphic: 0.736
+device: 0.679
+other: 0.555
+semantic: 0.442
+network: 0.323
+assembly: 0.286
+socket: 0.242
+boot: 0.214
+vnc: 0.198
+KVM: 0.114
+
+incorrect handling of [r32] address (long mode)
+
+while executing in Long Mode (x86-64) instructions such as
+
+mov eax,[r15d]
+
+end up executing as
+
+mov eax,[r15]
+
+according to x86 programmer manuals the behavior of using the Address-Size override (in long mode) is supposed to ignore the high 32bits of the register. I use this fact in my operating system to reduce register usage (the high 32 bits of r15 holds other data). consequently a general protection exception occurs since the memory address isn't "canonical". this error doesn't always appear since the high 32 bits might not be zero in those conditions.
+
+You are correct about what the instruction is supposed to do. That said the behaviour you describe is not reproducible. Which version of QEMU are you using? Could you please send a testcase?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+