libjava status on Solaris 8/Intel and IRIX 6.5

[Rainer Orth]

Rainer Orth writes:

> mips-sgi-irix6.5 (N32 only, I'll post N64/-mabi=64 results when that run
> finishes):

and here are the N64 results, with -ldl removed from the libgcj.spec until
the testsuite uses the proper spec file corresponding to the multilib under
test:

                === libjava Summary ===

# of expected passes            1908
# of unexpected failures        36
# of expected failures          18
# of untested testcases         111

FAIL: PR5902 compilation from bytecode
FAIL: PR5902 -O compilation from bytecode
FAIL: calls output
FAIL: martin output
FAIL: throwit output
FAIL: linking cxxtest
FAIL: Invoke_1 execution from source compiled test
FAIL: Invoke_1 execution from bytecode->native test
FAIL: Invoke_1 -O execution from source compiled test
FAIL: Invoke_1 -O execution from bytecode->native test
FAIL: PR218 execution from source compiled test
FAIL: PR218 execution from bytecode->native test
FAIL: PR218 -O execution from source compiled test
FAIL: PR218 -O execution from bytecode->native test
FAIL: invokethrow output from source compiled test
FAIL: invokethrow output from bytecode->native test
FAIL: invokethrow -O output from source compiled test
FAIL: invokethrow -O output from bytecode->native test
FAIL: test_long output from bytecode->native test
FAIL: test_long -O output from bytecode->native test
FAIL: TLtest compilation from bytecode
FAIL: TLtest -O compilation from bytecode
FAIL: Array_3 execution from source compiled test
FAIL: Array_3 execution from bytecode->native test
FAIL: Array_3 -O execution from source compiled test
FAIL: Array_3 -O execution from bytecode->native test
FAIL: FileHandleGcTest execution from source compiled test
FAIL: FileHandleGcTest execution from bytecode->native test
FAIL: FileHandleGcTest -O execution from source compiled test
FAIL: FileHandleGcTest -O execution from bytecode->native test
FAIL: ArrayStore -O output from source compiled test
FAIL: ArrayStore -O execution from bytecode->native test
FAIL: InvokeReturn output from source compiled test
FAIL: InvokeReturn output from bytecode->native test
FAIL: InvokeReturn -O output from source compiled test
FAIL: InvokeReturn -O output from bytecode->native test

This doesn't look much worse than the N32 results

	http://gcc.gnu.org/ml/java/2002-03/msg00389.html
and
	http://gcc.gnu.org/ml/java/2002-03/msg00392.html

Compared to the N32 results, there are 7 new failures and a couple of changes:

+FAIL: calls output
+FAIL: martin output
+FAIL: throwit output

-FAIL: invokethrow execution from source compiled test
-FAIL: invokethrow execution from bytecode->native test
-FAIL: invokethrow -O execution from source compiled test
-FAIL: invokethrow -O execution from bytecode->native test
+FAIL: invokethrow output from source compiled test
+FAIL: invokethrow output from bytecode->native test
+FAIL: invokethrow -O output from source compiled test
+FAIL: invokethrow -O output from bytecode->native test

+FAIL: Array_3 -O execution from source compiled test

-FAIL: ArrayStore -O execution from source compiled test
+FAIL: ArrayStore -O output from source compiled test

+FAIL: InvokeReturn output from source compiled test
+FAIL: InvokeReturn output from bytecode->native test
+FAIL: InvokeReturn -O output from source compiled test
+FAIL: InvokeReturn -O output from bytecode->native test

I'll have to investigate them, but this will probably have to wait, maybe
even after the 3.1 release.

	Rainer