summary refs log tree commit diff stats
path: root/results/classifier/zero-shot-user-mode/instruction/1283519
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-08 13:28:15 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-07-08 13:28:28 +0200
commit5aa276efcbd67f4300ca1a7f809c6e00aadb03da (patch)
tree9b8f0e074014cda8d42f5a97a95bc25082d8b764 /results/classifier/zero-shot-user-mode/instruction/1283519
parent1a3c4faf4e0a25ed0b86e8739d5319a634cb9112 (diff)
downloademulator-bug-study-5aa276efcbd67f4300ca1a7f809c6e00aadb03da.tar.gz
emulator-bug-study-5aa276efcbd67f4300ca1a7f809c6e00aadb03da.zip
restructure results
Diffstat (limited to 'results/classifier/zero-shot-user-mode/instruction/1283519')
-rw-r--r--results/classifier/zero-shot-user-mode/instruction/128351916
1 files changed, 16 insertions, 0 deletions
diff --git a/results/classifier/zero-shot-user-mode/instruction/1283519 b/results/classifier/zero-shot-user-mode/instruction/1283519
new file mode 100644
index 00000000..fe57aa4b
--- /dev/null
+++ b/results/classifier/zero-shot-user-mode/instruction/1283519
@@ -0,0 +1,16 @@
+instruction: 0.888
+syscall: 0.074
+runtime: 0.038
+
+
+
+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