[Bug testsuite/33263] [4.3/4.4 regression] libjava testsuite failures on alpha-linux

["ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>]

------- Comment #7 from ubizjak at gmail dot com  2009-01-07 14:02 -------
(In reply to comment #0)

> FAIL: natgetargssize.cc compilation
> FAIL: natgetlocalvartable.cc compilation
> FAIL: natgetstacktrace.cc compilation
> FAIL: natevents.cc compilation
> FAIL: natgetallthreads.cc compilation
> FAIL: natgeterrorname.cc compilation
> FAIL: natgetmethodname.cc compilation

These are in fact due to PR31488.

> FAIL: Array_3 execution - source compiled test
> FAIL: Array_3 -findirect-dispatch execution - source compiled test
> FAIL: Array_3 -O3 execution - source compiled test
> FAIL: Array_3 -O3 -findirect-dispatch execution - source compiled test
> FAIL: G19990303_02 execution - source compiled test
> FAIL: G19990303_02 -findirect-dispatch execution - source compiled test
> FAIL: G19990303_02 -O3 execution - source compiled test
> FAIL: G19990303_02 -O3 -findirect-dispatch execution - source compiled test
> FAIL: Invoke_1 execution - source compiled test
> FAIL: Invoke_1 -findirect-dispatch execution - source compiled test
> FAIL: Invoke_1 -O3 execution - source compiled test
> FAIL: Invoke_1 -O3 -findirect-dispatch execution - source compiled test
> FAIL: N19990310_02 -O3 output - source compiled test
> FAIL: N19990310_02 -O3 -findirect-dispatch output - source compiled test
> FAIL: PR218 output - source compiled test
> FAIL: PR218 -O3 output - source compiled test
> FAIL: StackTrace2 execution - source compiled test
> FAIL: StackTrace2 -findirect-dispatch execution - source compiled test
> FAIL: StackTrace2 -O3 execution - source compiled test
> FAIL: StackTrace2 -O3 -findirect-dispatch execution - source compiled test
> FAIL: Throw_2 execution - source compiled test
> FAIL: Throw_2 -findirect-dispatch execution - source compiled test
> FAIL: Throw_2 -O3 execution - source compiled test
> FAIL: Throw_2 -O3 -findirect-dispatch execution - source compiled test
> FAIL: Throw_3 output - source compiled test
> FAIL: Throw_3 -findirect-dispatch output - source compiled test
> FAIL: Throw_3 -O3 output - source compiled test
> FAIL: Throw_3 -O3 -findirect-dispatch output - source compiled test
> FAIL: initexc execution - source compiled test
> FAIL: initexc -findirect-dispatch execution - source compiled test
> FAIL: initexc -O3 execution - source compiled test
> FAIL: initexc -O3 -findirect-dispatch execution - source compiled test
> FAIL: invokethrow execution - source compiled test
> FAIL: invokethrow -findirect-dispatch output - source compiled test
> FAIL: invokethrow -O3 execution - source compiled test
> FAIL: invokethrow -O3 -findirect-dispatch output - source compiled test
> FAIL: pr83 -findirect-dispatch execution - source compiled test
> FAIL: pr83 -O3 -findirect-dispatch execution - source compiled test

These are due to some strange failure in dejagnu framework on debian alpha.
>From my private communication with Matthias Close:

--quote--
I'm trying to fix last remaining gcc testsuite errors [0] on Debian
alpha gcc (gcc30 cfarm machine) and I tripped on some strange
dejagnu/Expect/Tcl error on Debian system.

This problem causes following teststuite failures:

FAIL: g++.dg/ext/cleanup-10.C execution test
FAIL: g++.dg/ext/cleanup-11.C execution test
FAIL: g++.dg/ext/cleanup-8.C execution test
FAIL: g++.dg/ext/cleanup-9.C execution test

FAIL: gcc.dg/cleanup-10.c execution test
FAIL: gcc.dg/cleanup-11.c execution test
FAIL: gcc.dg/cleanup-8.c execution test
FAIL: gcc.dg/cleanup-9.c execution test

and all remaining libjava test failures, FWIW.

These runtime testcases (including java) all work OK when executed
directly from the shell (using just built libraries, so all libraries
are exactly the same), but fail when run from dejagnu framework. They
also fail when executing these test cases through dejagnu with default
installed compiler (gcc-4.2.4).

The problem is, that SIGSEGV handling is somehow suppressed when run
from dejagnu framework. To check this, please put attached sig.c to
gcc/testsuite/dg.exp directory and execute "make -k check-gcc
RUNTESTFLAGS=dg.exp=sig.c" from gcc/ subdirectory of your build dir.
The testcase will fail, OTOH, it will finish without problems when
executed directly from the shell.

I have noticed, that in some of your testreports, these strange
failures happen [1], but some of your testreports doesn't show them
[2], [3]. Are these tests performed on the same machine? If not, what
is the difference with runtime/testing environments between these test
runs?

[0] http://gcc.gnu.org/ml/gcc-testresults/2008-12/msg02551.html
[1] http://gcc.gnu.org/ml/gcc-testresults/2009-01/msg00182.html
[2] http://gcc.gnu.org/ml/gcc-testresults/2008-12/msg01836.html
[3] http://gcc.gnu.org/ml/gcc-testresults/2008-12/msg00926.html
--/quote--

--quote2--
The question is, why we abort on following dejagnu testcase on alpha systems:

--cut here--

/* { dg-do run } */

#include <stdlib.h>
#include <signal.h>

char *null;

static void fn4 (int sig)
{
 exit (0);
}

int main()
{  signal (SIGSEGV, fn4);
 *null = 0;
 abort ();
}

--cut here--

When this test is executed via dejagnu framework from i.e. gcc/testsuite/gcc.dg
directory using


make -k check-gcc RUNTESTFLAGS=dg.exp=sig.c

from gcc subdir of the build dir, the SEGV redirection is simply ignored and
testcase aborts in the last line, although exactly the same binary works fine
when executed from the command prompt.

This problem causes follwing spurious java testsuite failures (in addition to
failures mentioned below):

FAIL: TestClosureGC run
FAIL: Array_3 execution - source compiled test
FAIL: Array_3 -findirect-dispatch execution - source compiled test
FAIL: Array_3 -O3 execution - source compiled test
FAIL: Array_3 -O3 -findirect-dispatch execution - source compiled test
FAIL: Invoke_1 execution - source compiled test
FAIL: Invoke_1 -findirect-dispatch execution - source compiled test
FAIL: Invoke_1 -O3 execution - source compiled test
FAIL: Invoke_1 -O3 -findirect-dispatch execution - source compiled test
FAIL: PR218 output - source compiled test
FAIL: PR218 -O3 output - source compiled test
FAIL: StackTrace2 execution - source compiled test
FAIL: StackTrace2 -findirect-dispatch execution - source compiled test
FAIL: StackTrace2 -O3 execution - source compiled test
FAIL: StackTrace2 -O3 -findirect-dispatch execution - source compiled test
FAIL: Throw_2 execution - source compiled test
FAIL: Throw_2 -findirect-dispatch execution - source compiled test
FAIL: Throw_2 -O3 execution - source compiled test
FAIL: Throw_2 -O3 -findirect-dispatch execution - source compiled test
FAIL: Throw_3 output - source compiled test
FAIL: Throw_3 -findirect-dispatch output - source compiled test
FAIL: Throw_3 -O3 output - source compiled test
FAIL: Throw_3 -O3 -findirect-dispatch output - source compiled test
FAIL: pr83 -findirect-dispatch execution - source compiled test
FAIL: pr83 -O3 -findirect-dispatch execution - source compiled test

This is on gcc30 CompileFarm machine, see http://gcc.gnu.org/wiki/CompileFarm
--/quote2--

Confirmed as a testsuite framework problem.


-- 

ubizjak at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |31488
             Status|UNCONFIRMED                 |NEW
          Component|libgcj                      |testsuite
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2009-01-07 14:02:20
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33263