[Bug classpath/28570] JNI on ARM: float parameters are not correctly passed to java methods

[s_j_newbury at yahoo dot co dot uk]

------- Comment #5 from s_j_newbury at yahoo dot co dot uk  2007-08-22 11:10 
-------
This may be the same bug?

With jamvm-1.45, using the test from comment #6 of bug
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22800

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

However this does not happen with jamvm compiled -O0.  Furthermore, starting
from -O0, turning each optimization on as listed in the gcc info documentation
for -O1 also works!?!  Or does -O0 override later flags?


-- 

s_j_newbury at yahoo dot co dot uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |s_j_newbury at yahoo dot co
                   |                            |dot uk


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