blob: f83be0e039e715eae11fa85e98adac772198cd85 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
graphic: 0.881
vnc: 0.879
performance: 0.678
device: 0.639
semantic: 0.611
socket: 0.441
boot: 0.416
PID: 0.407
permissions: 0.392
network: 0.348
files: 0.310
other: 0.308
debug: 0.256
KVM: 0.077
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?
Hi Christophe -- we think that commit bd49e6027cbc207c, now in master, should have fixed this bug. Could you retry your testcase with a QEMU build including that fix?
I updated my QEMU git tree such that it includes commit bd49e6027cbc207c, and the test now passes.
Thanks for the prompt fix!
|