Bug#467486: Investigations about failure

Michael Koch konqueror at gmx.de
Thu Apr 10 08:20:04 UTC 2008


On Thu, Apr 10, 2008 at 10:06:20AM +0200, Andreas Kirschbaum wrote:
> gcc-4.2 and gcc-4.3 differ in the representation of char values: gcc-4.2
> represents a char as a 32 bit value (bits 0..7 is the char value; bits
> 8..31 are always set to zero); gcc-4.3 uses only the lower 8 bits,
> ignoring bits 8..31.
> 
> kaffe defines "typedef unsigned char jboolean;" in
> kaffe-1.1.8/libraries/javalib/external/classpath/include/jni_md-x86-linux-gnu.h
> but assumes %eax is 0/1 in compiled Java code. This makes compiled Java
> code calling into native C code almost always assume "true" for jboolean
> return values due to the non-zero "garbage" in bits 8..31.

Can you take a look into kaffe 1.1.9 (not packaged yet due to different
problems) if that is fixed? I haven't found the time yet for this)


Cheers,
Michael





More information about the pkg-java-maintainers mailing list