This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: About testing other languages: was RE: [C++ PATCH, committed] Fix libstdc++ regressions due to my access checking changes


Andrew Haley writes:

> This trained eye wants to know what the failures are.

See e.g. my latest IRIX 6.5 mainline results:

	http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00424.html

For the N32 ABI (-mabi=n32):

spawn [open ...]
/proc open failed
FAIL: FileHandleGcTest execution - source compiled test

FAIL: FileHandleGcTest execution - bytecode->native test
FAIL: FileHandleGcTest -O execution - source compiled test
FAIL: FileHandleGcTest -O execution - bytecode->native test

spawn [open ...]
FAIL: TestProxy execution - source compiled test

FAIL: TestProxy execution - bytecode->native test
FAIL: TestProxy -O execution - source compiled test
FAIL: TestProxy -O execution - bytecode->native test

spawn [open ...]
FAIL: Throw_2 execution - source compiled test

FAIL: Throw_2 execution - bytecode->native test
FAIL: Throw_2 -O execution - source compiled test
FAIL: Throw_2 -O execution - bytecode->native test
FAIL: invokethrow execution - source compiled test
FAIL: invokethrow execution - bytecode->native test
FAIL: invokethrow -O execution - source compiled test
FAIL: invokethrow -O execution - bytecode->native test

spawn [open ...]
java.lang.InternalError: Unexpected exception while defining class C
   <<No stacktrace available>>
Caused by: java.lang.NullPointerException
   <<No stacktrace available>>
PASS: /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestEarlyGC.exe execution - /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestEarlyGC.exe
FAIL: /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestEarlyGC.exe output - /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestEarlyGC.exe

spawn [open ...]
FAIL: /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestLeak.exe execution - /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestLeak.exe

spawn [open ...]
Exception in thread "main" java.lang.InternalError: Unexpected exception while defining class dummy
   <<No stacktrace available>>
Caused by: java.lang.NullPointerException
   <<No stacktrace available>>
FAIL: /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestMultiple.exe execution - /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestMultiple.exe

spawn [open ...]
Exception in thread "main" java.lang.InternalError: Unexpected exception while defining class dummy
   <<No stacktrace available>>
Caused by: java.lang.NullPointerException
   <<No stacktrace available>>
FAIL: /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestParent.exe execution - /amnt/figaro/volumes/obj-gcc/gcc/obj.irix5/gcc-3.4-20030402/6.5.18-gcc-java/mips-sgi-irix6.5/libjava/testsuite/TestParent.exe

The N64 ABI (-mabi=64) results are similar, with the addition of

spawn [open ...]
fail
FAIL: calls output

spawn [open ...]
Hello, Java
>From C
Goodbye, Java
FAIL: martin output

spawn [open ...]
class java.lang.UnknownError
null
class java.lang.Throwable
null
FAIL: throwit output

spawn [open ...]
true
true
?
63
63
274869875436
0.0
6.0E-312
PASS: InvokeReturn execution - source compiled test
FAIL: InvokeReturn output - source compiled test

At a glance, 3.3 results are identical

	http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00752.html

although I haven't compared them in detail.

I can certainly start investigating individual failures.

	Rainer

-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]