summary refs log tree commit diff stats
path: root/results/classifier/gemma3:27b/instruction/1283519
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-06 16:43:19 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-06 16:43:19 +0000
commit238ec2b7cc1557d6f34c33cc482e4d0cd3e266dd (patch)
treecd8a1b75ba7b3543eb7fe6857f408e7be4d9fd0b /results/classifier/gemma3:27b/instruction/1283519
parent96049c939b1916d80532630d63c14e04d5244f1d (diff)
downloadqemu-analysis-238ec2b7cc1557d6f34c33cc482e4d0cd3e266dd.tar.gz
qemu-analysis-238ec2b7cc1557d6f34c33cc482e4d0cd3e266dd.zip
add results
Diffstat (limited to 'results/classifier/gemma3:27b/instruction/1283519')
-rw-r--r--results/classifier/gemma3:27b/instruction/128351913
1 files changed, 13 insertions, 0 deletions
diff --git a/results/classifier/gemma3:27b/instruction/1283519 b/results/classifier/gemma3:27b/instruction/1283519
new file mode 100644
index 000000000..c65570d39
--- /dev/null
+++ b/results/classifier/gemma3:27b/instruction/1283519
@@ -0,0 +1,13 @@
+
+
+
+PowerPC altivec rounding instructions vrfi(m|n|z)not correctly mapped
+
+When using ppc-linux-user/qemu-ppc on a ppc ELF executable, I see that QEMU wrongly recognizes the vrfim, vrfin and vrfiz instructions:
+
+If the binary contains vrfim QEMU sees vrfiz
+If the binary contains vrfin QEMU sees vrfim
+If the binary contains vrfiz QEMU sees vrfin
+The vrfip instruction is correctly recognized.
+
+Those instructions normally round a floating-point altivec vector to zero (z), infinity (p), minus infinity (m) or nearest (n).
\ No newline at end of file