--- Additional Comments From robilad at kaffe dot org 2005-08-22 13:25
---
It seems to be clearly a bug in how some non-free implementation implements the
specifications.
Since Sun Microsystems has confirmed the bug in their implementation, and the
specification is clear on the matter,
--- Additional Comments From veldema at cs dot fau dot de 2005-08-22 12:18
---
Confirmed, this is a bug in SUN's JDK since 2001.
Perhaps a a bug should be introduced to make libgcj/classpath bug compatible ?
if (double_string == "0.00x" && x != '0') return return "0.00x0"
should do the
--- Additional Comments From veldema at cs dot fau dot de 2005-08-22 12:03
---
1) I will file a bug report with SUN and see what they say and report back here
2) I read the comments with _dtoa and for floats the arg is interpretted as
single-precision if mode >= 16 (seems for a double yo
--- Additional Comments From tromey at gcc dot gnu dot org 2005-08-19
16:20 ---
I agree that this is most likely not a libgcj bug.
Ronald, why do you think the _dtoa call ought to be changed?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23466
--- Additional Comments From robilad at kaffe dot org 2005-08-18 22:41
---
that looks like a bug in Sun's implementation, as the Double.toString() API
specs demand that Double.toString returns only as many digits as necessary to
uniquely identify the floating point number.
Adding one o
