blob: 0c0f8b13236258c273b8c8d7bfd1b1aa229beea1 (
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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
floating point emulation can fail to set FE_INEXACT
Floating point emulation can fail to set FE_INEXACT in some circumstances. This shows up quite often in glibc's "math" tests. A similar test is attached.
On ppc64le native:
--
$ gcc nextafter.c -o nextafter -lm
$ ./nextafter $(./nextafter)
0x0000000000000001 0.000000
0x0
0xa000000
FE_INEXACT FE_UNDERFLOW
0x0000000000000000 0.000000
--
On x86_64:
--
$ gcc nextafter.c -o nextafter -lm
$ ./nextafter $(./nextafter)
0x0000000000000001 0.000000
0x0
0x30
FE_INEXACT FE_UNDERFLOW
0x0000000000000000 0.000000
--
Using qemu-system-ppc64
--
$ ./nextafter $(./nextafter)
0x0000000000000001 0.000000
0x0
0x8000000
FE_UNDERFLOW
0x0000000000000000 0.000000
--
Using qemu-x86_64:
--
$ ./nextafter $(./nextafter)
0x0000000000000001 0.000000
0x0
0x0
0x0000000000000000 0.000000
--
QEMU versions vary, but not too much, and are pretty close to git HEAD:
- 586f3dced9 (HEAD -> master, origin/master, origin/HEAD) Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190822' into staging
- 864ab31 Update version for v4.1.0-rc4 release
Since the issue happens nearly identically on different targets, I suspect the issue lies somewhere in fpu/softfloat.c.
|