spawn /test/gnu/gcc/objdir/gcc/testsuite/gfortran/../../gfortran -B/test/gnu/gcc/objdir/ gcc/testsuite/gfortran/../../ -B/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/ /test/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/class_allocate_18.f90 -fno-diagnostics-show- caret -fdiagnostics-color=never -O0 -fsanitize=undefined -B/test/gnu/gcc/objdir/hppa64-h p-hpux11.11/./libgfortran/.libs -L/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran /.libs -L/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/.libs -L/test/gnu/gcc/ob jdir/hppa64-hp-hpux11.11/./libatomic/.libs -B/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./ libquadmath/.libs -L/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libquadmath/.libs -L/test /gnu/gcc/objdir/hppa64-hp-hpux11.11/./libquadmath/.libs -lm -o ./class_allocate_18.exe ld: Can't find library for -lubsan Fatal error. collect2: error: ld returned 1 exit status compiler exited with status 1 output is: ld: Can't find library for -lubsan Fatal error. collect2: error: ld returned 1 exit status FAIL: gfortran.dg/class_allocate_18.f90 -O0 (test for excess errors)
I think this has been fixed by r220181.
Outside of the testsuite I don't see a failure. Running the testsuite I do. Running /home/jerry/gcc/trunk/gcc/testsuite/gfortran.dg/dg.exp ... FAIL: gfortran.dg/class_allocate_18.f90 -O0 execution test FAIL: gfortran.dg/class_allocate_18.f90 -O1 execution test FAIL: gfortran.dg/class_allocate_18.f90 -O2 execution test FAIL: gfortran.dg/class_allocate_18.f90 -O3 -fomit-frame-pointer execution test FAIL: gfortran.dg/class_allocate_18.f90 -O3 -fomit-frame-pointer -funroll-loops execution test FAIL: gfortran.dg/class_allocate_18.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions execution test FAIL: gfortran.dg/class_allocate_18.f90 -O3 -g execution test FAIL: gfortran.dg/class_allocate_18.f90 -Os execution test
(In reply to Jerry DeLisle from comment #2) > Outside of the testsuite I don't see a failure. Running the testsuite I do. Try to run executable under valgrind.
(In reply to Uroš Bizjak from comment #3) > (In reply to Jerry DeLisle from comment #2) > > Outside of the testsuite I don't see a failure. Running the testsuite I do. > > Try to run executable under valgrind. FYI, also happens on i686-linux-gnu [1]. [1] https://gcc.gnu.org/ml/gcc-testresults/2015-02/msg00059.html
Valgrind shows 5 instances of: ==20889== Invalid read of size 8 ==20889== at 0x401241: __final_main_T2.3409 (in /home/jerry/prs/pr64506/a.out) ==20889== by 0x400D51: __final_main_T3.3400 (in /home/jerry/prs/pr64506/a.out) ==20889== by 0x400EF5: MAIN__ (in /home/jerry/prs/pr64506/a.out) ==20889== by 0x40147C: main (in /home/jerry/prs/pr64506/a.out)
Duplicate or pr64921. *** This bug has been marked as a duplicate of bug 64921 ***