https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86571
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot
gnu.org
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
The test below fails because of this discrepancy:
FAIL: gcc.dg/torture/builtin-sprintf.c -O0 execution test
GCC should relax the upper bound on the amount of output for NaN. The standard
specifies two forms of output "nan" or "nan(n-char-sequence)" The latter
doesn't seem to be output by any known implementations (plus the length of the
n-char-sequence is unspecified, making it useless for portability) and there
have been voices to deprecate or remove it from the C standard. I plan to
propose one of the two for C2X. Until then, bumping up the upper bound either
for all targets, or just for AIX (under some sort of a target hook) is probably
the best solution.
