[kaffe] Testing for 1.1.0 release

[mcmahill@mtl.mit.edu]

On Tue, 20 May 2003, Dalibor Topic wrote:

> Of the six I'm getting two times a weird
> 
> error compiling:
> /tmp/topic/build/kaffe/kaffe/../kaffevm/.libs/libkaffevm-1.1.x-cvs.so:
> Undefined PLT symbol "startMethods" (reloc type = 26, symnum = 63)
> FAIL: ThreadInterrupt.java
> 
> error compiling:
> /tmp/topic/build/kaffe/kaffe/../kaffevm/.libs/libkaffevm-1.1.x-cvs.so:
> Undefined PLT symbol "hashRemove" (reloc type = 26, symnum = 348)
> FAIL: NoClassDefTest.java
> 
> The other failures are:
> 
> bash-2.05$ ls -1 test/regression/*.fail
> test/regression/CLTestLie.fail
> test/regression/ClassGC.fail (* cross platform)
> test/regression/IndexTest.fail
> test/regression/ProcessClassTest.fail (* cross platform)


I only fail 3 of 133 now on my alpha (NetBSD-1.6.1)

% ls -1 test/regression/*.fail
test/regression/ClassGC.fail
test/regression/InetSocketAddressTest.fail
test/regression/ProcessClassTest.fail



> --- mcmahill@mtl.mit.edu wrote:
> 
> > > * and try to figure out why the SIGFPE happens when 4.9e-324 is compared
> > > against some other value. ;)
> > 
> > this usually happens when you do a floating point operation on an
> > unitialized variable.  like
> > 
> > foo() {
> > double x;
> > 
> > if(x >= 3.2)
> > ....
> > 
> > the debugger will often show 'x' as having a value of something like
> > 4.9e-324.
> > 


> > DoubleComp.fail - probably wants IEEE-754 math.  To get this add -mieee to
> > CFLAGS.
> 
> yep, that worked, thanks. In fact, it also fixed the problem above.

but I suspect there was an underlying bug with an unitialized value in
addition to needing IEEE support.

> 
> > LostFrame.fail  - which version of NetBSD are you on?  1.6 had some bugs
> > in ld.so_elf.  Should be fixed in 1.6.1
> 
> bash-2.05$ uname -a
> NetBSD spe159.testdrive.compaq.com 1.6 NetBSD 1.6 (GENERIC). what's the status
> on 1.6.1?

It has been released.  Maybe compaq could be persuaded to update their
testdrive box.

-Dan