summary refs log tree commit diff stats
path: root/results/classifier/zero-shot-user-mode/instruction/1761401
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/1761401
parent1a3c4faf4e0a25ed0b86e8739d5319a634cb9112 (diff)
downloadqemu-analysis-5aa276efcbd67f4300ca1a7f809c6e00aadb03da.tar.gz
qemu-analysis-5aa276efcbd67f4300ca1a7f809c6e00aadb03da.zip
restructure results
Diffstat (limited to 'results/classifier/zero-shot-user-mode/instruction/1761401')
-rw-r--r--results/classifier/zero-shot-user-mode/instruction/176140116
1 files changed, 16 insertions, 0 deletions
diff --git a/results/classifier/zero-shot-user-mode/instruction/1761401 b/results/classifier/zero-shot-user-mode/instruction/1761401
new file mode 100644
index 000000000..27bd12965
--- /dev/null
+++ b/results/classifier/zero-shot-user-mode/instruction/1761401
@@ -0,0 +1,16 @@
+instruction: 0.601
+runtime: 0.202
+syscall: 0.198
+
+
+
+ARM/Neon: vcvt rounding error
+
+Hello,
+
+While using QEMU commit 47d3b60858d90ac8a0cc3a72af7f95c96781125a (March 28, 2018), I've noticed failures in one of the GCC ARM/Neon tests. The test passes on hardware, and with QEMU-2.11.0, so it looks like a recent regression.
+
+The test builds a vector of 4 float32 with "125.9" as value, then converts them to 4 uint32_t.
+The expected result is 125, but we get 126 instead.
+
+Maybe it's just a matter of default rounding mode?
\ No newline at end of file