JNI bug?

Mon Jan 29 18:45:00 GMT 2007

Andrew Haley wrote:
> Marco Trudel writes:
> > Andrew Haley wrote:
> > > Marco Trudel writes:
> > > > Andrew Haley wrote:
> > > > > 
> > > > > Err, *why* are you doing this weird thing, anyway? Why not pass the correct type?
> > > > 
> > > > The same old story: I use a library which does it wrong... Someone has 
> > > > to test all these libraries out there ;-)
> > > > The other reason that I always run into problems is that I develop with 
> > > > a Sun JDK and deploy with GCJ...
> > > 
> > > Each to their own. Anyway, I don't think gcj is buggy here, but I'd
> > > happily accept a patch that masks off the low-order bits before
> > > calling the native code.
> > 
> > Just kicked on my Linux box and tried it. Fails with a static and shared 
> > GCJ... So, the old 32bit <-> 64bit story?
>> Almost certainly.

Yeah... What else...
You know, you use a too recent computer! ;-)
> > I only have 32bit computers here...
>> How very 20th Century. :-)

Actually, I didn't even know there are already 64bit computers out
there... I also recently read about dual-core computers! Unbelievable,
only 23 and already way behind the time...
But the question remains: What to do about this? I have no idea where to
look for this problem or what to do against. I would like to have the
same behavior, but it's not worth it if it's a huge thing to implement...
Marco