bug-classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug classpath/22800] ARM double to ascii conversion issue


From: s_j_newbury at yahoo dot co dot uk
Subject: [Bug classpath/22800] ARM double to ascii conversion issue
Date: 21 Aug 2007 21:03:48 -0000


------- Comment #24 from s_j_newbury at yahoo dot co dot uk  2007-08-21 21:03 
-------
(In reply to comment #23)
> This is still not working for me (arm-iwmmxt-linux-gnueabi).  With jamvm-1.45 
> +
> gnu-classpath-0.93 and gnu-classpath trunk as of 20070821; using the test from
> comment #6 I get:
> 
> a equals b:true
> a:-1.0
> b:-1.0
> Double.doubleToLongBits(a):-4616189618054758400
> Double.doubleToLongBits(a):-4616189618054758400
> Double.doubleToRawLongBits(b):-4616189618054758400
> Double.doubleToRawLongBits(b):-4616189618054758400
> Float.floatToRawIntBits((float)a):-1082130432
> Float.floatToIntBits((float)a):-1082130432
> Float.floatToRawIntBits((float)b):-1082130432
> Float.floatToIntBits((float)b):-1082130432
> jamvm: java_lang_VMDouble.c:430: Java_java_lang_VMDouble_toString: Assertion
> `least_necessary_precision <= maximal_precision' failed.
> Aborted
> zaurus java # 
> 
> Meanwhile with gcj and gij (20070810 + ARM EABI patches) on the same system, I
> get:
> a equals b:true
> a:-1.0
> b:-1.0
> Double.doubleToLongBits(a):-4616189618054758400
> Double.doubleToLongBits(a):-4616189618054758400
> Double.doubleToRawLongBits(b):-4616189618054758400
> Double.doubleToRawLongBits(b):-4616189618054758400
> Float.floatToRawIntBits((float)a):-1082130432
> Float.floatToIntBits((float)a):-1082130432
> Float.floatToRawIntBits((float)b):-1082130432
> Float.floatToIntBits((float)b):-1082130432
> a div b:Infinity
> a:1.002
> b:0.0
> Double.doubleToLongBits(a):4607191425999272149
> Double.doubleToLongBits(a):4607191425999272149
> Double.doubleToRawLongBits(b):0
> Double.doubleToRawLongBits(b):0
> Float.floatToRawIntBits((float)a):1065369993
> Float.floatToIntBits((float)a):1065369993
> Float.floatToRawIntBits((float)b):0
> Float.floatToIntBits((float)b):0
> a:8.8888888E21
> b:5.5555555E-21
> Double.doubleToLongBits(a):4935415097293273796
> Double.doubleToLongBits(a):4935415097293273796
> Double.doubleToRawLongBits(b):4303818644414190050
> Double.doubleToRawLongBits(b):4303818644414190050
> Float.floatToRawIntBits((float)a):1676734222
> Float.floatToIntBits((float)a):1676734222
> Float.floatToRawIntBits((float)b):500294153
> Float.floatToIntBits((float)b):500294153
> 
> In both cases it is the same bytecode compiled with ecj-3.3
> 

Actually now I see them both on the same page it looks like a different bug...?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22800





reply via email to

[Prev in Thread] Current Thread [Next in Thread]