[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
sgk at troutmask dot apl.washington.edu
gcc-bugzilla@gcc.gnu.org
Mon Jul 9 19:33:00 GMT 2018
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #2 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, Jul 09, 2018 at 07:20:02PM +0000, ebotcazou at gcc dot gnu.org wrote:
>
> The correct invocation of a GCC testsuite is "make -k check-blah", otherwise
> the recursive Make processes will stop on errors.
>
Since when? I've been doing 'gmake check-fortran' and
'gmake -j6 check-fortran' for more than 15 years. There
was never an error. This broke recently.
I just did a bootstrap of the 8-branch. 'gmake -j6 check-fortran'
completes without an error. The last few line are
=== gfortran Summary ===
# of expected passes 6413
# of expected failures 18
# of unsupported tests 2
/safe/sgk/gcc/obj8/gcc/gfortran version 8.1.1 20180709 (GCC)
gmake[2]: Leaving directory '/safe/sgk/gcc/obj8/gcc'
gmake[1]: Leaving directory '/safe/sgk/gcc/obj8/gcc'
Something is broken with trunk. These do not occur on
the 8-branch.
gmake[4]: *** [Makefile:306: check-DEJAGNU] Error 1
gmake[4]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp/testsuite'
gmake[3]: *** [Makefile:350: check-am] Error 2
gmake[3]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp
More information about the Gcc-bugs
mailing list