Remove the test that ensures that when the string "nan(...)" is converted
to floating-point, the result is a quiet NaN. The current implementation may return a signaling NaN, and the vendor has no plans for changing this, for reasons explained in the comment I added.
This commit is contained in:
parent
29d7c2fce5
commit
f56f1d7735
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=165754
@ -190,7 +190,15 @@ main(int argc, char *argv[])
|
|||||||
assert(f != f);
|
assert(f != f);
|
||||||
assert(d != d);
|
assert(d != d);
|
||||||
assert(ld != ld);
|
assert(ld != ld);
|
||||||
|
#if 0
|
||||||
|
/*
|
||||||
|
* POSIX says we should only generate quiet NaNs, but the gdtoa
|
||||||
|
* author convincingly argues that if you ask for a NaN format
|
||||||
|
* based on some implementation-defined string, you should get
|
||||||
|
* what you asked for, even if it's a signaling NaN.
|
||||||
|
*/
|
||||||
assert(fetestexcept(FE_INVALID) == 0);
|
assert(fetestexcept(FE_INVALID) == 0);
|
||||||
|
#endif
|
||||||
|
|
||||||
printf("ok 2 - scanfloat\n");
|
printf("ok 2 - scanfloat\n");
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user