This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Mauve - the remainder
- From: Andrew Haley <aph at cambridge dot redhat dot com>
- To: Mark Wielaard <mark at klomp dot org>
- Cc: java at gcc dot gnu dot org
- Date: Thu, 18 Apr 2002 09:14:59 +0100 (BST)
- Subject: Mauve - the remainder
- References: <1019080941.7866.133.camel@elsschot>
Mark Wielaard writes:
> Hi,
>
> It seems that the slippage of GCC 3.1 was a positive thing for Mauve
> regression test fixing. On i686-pc-linux-gnu there are only 6 unanalyzed
> failures left. (And Andrew is chasing the extra failures on powerpc).
>
> Since I don't know how much time I will have till the actual release I
> will list the remaining issues. Maybe someone can help analyze and/or
> fix them.
>
> FAIL: gnu.testlet.java.lang.Double.DoubleTest: Error: test_intValue
> returned wrong results CYGNUS: Float to int conversions - 1 (number 1)
>
> When compiling to byte-code the following prints zero:
>
> public class DT
> {
> public static void main(String[] args)
> {
> System.out.println((int) 3.4e+32);
> }
> }
>
> The actual buyte-code produced contains the zero. It should print
> 2147483647 (maxint), which it does when compiling from source.
>
> FAIL: gnu.testlet.java.lang.Double.DoubleTest: Error: test_longValue
> returned wrong results CYGNUS: Float to int conversions - 1 (number 1)
>
> Same kind of failure, but now for (long) 3.4e+32. The byte-code contains
> -4294967296 but the result should be 9223372036854775807 (maxlong).
> Compiling from source gives the correct result.
>
> FAIL: gnu.testlet.java.lang.Float.FloatTest: Error: test_intValue
> returned wrong results - 1 (number 1)
>
> Same for (int) 3.4e+32f.
>
> Simple testcase for above failures attached. It succeeds when compiling
> from source, it fails when compiling to byte-code.
These look like the bugs I'm working on.
Andrew.