summary refs log tree commit diff stats
path: root/results/classifier/zero-shot-user-mode/output/instruction/1370
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-07 17:23:11 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-07 17:23:11 +0000
commitc50b0c4da17b6e83640e4ed2380fffb5f507c846 (patch)
treeb4f203fce1380e2ea3578a784bb8ee060fe42cbd /results/classifier/zero-shot-user-mode/output/instruction/1370
parent61361f925d4914a6608a0076e64cc2399311ed5f (diff)
downloadqemu-analysis-c50b0c4da17b6e83640e4ed2380fffb5f507c846.tar.gz
qemu-analysis-c50b0c4da17b6e83640e4ed2380fffb5f507c846.zip
add zero-shot results
Diffstat (limited to 'results/classifier/zero-shot-user-mode/output/instruction/1370')
-rw-r--r--results/classifier/zero-shot-user-mode/output/instruction/137019
1 files changed, 19 insertions, 0 deletions
diff --git a/results/classifier/zero-shot-user-mode/output/instruction/1370 b/results/classifier/zero-shot-user-mode/output/instruction/1370
new file mode 100644
index 000000000..1a7ba6455
--- /dev/null
+++ b/results/classifier/zero-shot-user-mode/output/instruction/1370
@@ -0,0 +1,19 @@
+instruction: 0.864
+runtime: 0.090
+syscall: 0.046
+
+
+
+x86 BLSI and BLSR semantic bug
+Description of problem:
+The result of instruction BLSI and BLSR is different from the CPU. The value of CF is different.
+Steps to reproduce:
+1. Compile this code
+```
+void main() {
+    asm("blsi rax, rbx");
+}
+```
+2. Execute and compare the result with the CPU. The value of `CF` is exactly the opposite. This problem happens with BLSR, too.
+Additional information:
+This bug is discovered by research conducted by KAIST SoftSec.