This is the mail archive of the mauve-discuss@sources.redhat.com mailing list for the Mauve project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Bug in DoubleTest/FloatTest?

From: Eric Blake <ebb9 at email dot byu dot edu>
To: Andrew Haley <aph at redhat dot com>
Cc: Stephen Crawley <crawley at dstc dot edu dot au>, mauve-discuss at sources dot redhat dot com
Date: Fri, 27 Sep 2002 12:35:11 -0600
Subject: Re: Bug in DoubleTest/FloatTest?
References: <200209271530.g8RFUD4s025073@piglet.dstc.edu.au><15764.31452.487090.269672@cuddles.cambridge.redhat.com>

Andrew Haley wrote:

Right.  The JDK has done this for a long while.

 >   4)  Leave it alone.

Yes: the JDK does not meet its specfication.

There are several other known cases where the JDK does not meet its own specs. The jacks compiler test suite (from the same location as the jikes compiler) highlights a few of those - and since javac uses the JDK when compiling, it creates miscompiled .class files! If you search Sun's bug database, you will find more mention of this problem in their reference implementation.

For example, the JDK is wrong on:
""+123456789f (it should be "1.2345679E8", not "1.23456792E8")
""+9.999999999999999e22 ("1.0E23", not "9.999999999999999E22")

--
This signature intentionally left boring.

Eric Blake ebb9@email.byu.edu
BYU student, free software programmer

Follow-Ups:
- Re: Bug in DoubleTest/FloatTest?
  - From: Stephen Crawley

References:
- Bug in DoubleTest/FloatTest?
  - From: Stephen Crawley
- Bug in DoubleTest/FloatTest?
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]