https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109135
--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Tue, Mar 14, 2023 at 10:36:27PM +0000, sgk at troutmask dot apl.washington.edu wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109135 > > --- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- > On Tue, Mar 14, 2023 at 10:25:53PM +0000, pinskia at gcc dot gnu.org wrote: > > > > --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- > > This is not a testsuite issue but rather the issue is the lto code is > > calling > > make ... > > > > That explains why groping around in gcc/testsuite for > a rogue make or MAKE was coming up empty. > > I'm in the middle of doing a serial 'gmake check-fortran', > which takes a long time on my system. Is there a way > to invoke only lto testing? > Answered my own question. % gmake RUNTESTFLAGS="dg.exp=pr71526.f90" check-fortran ... === gfortran Summary === # of expected passes 1 % gmake -j 1 RUNTESTFLAGS="dg.exp=pr71526.f90" check-fortran ... === gfortran Summary === # of expected passes 1 % gmake -j 2 RUNTESTFLAGS="dg.exp=pr71526.f90" check-fortran ... FAIL: gfortran.dg/pr71526.f90 -O (test for excess errors) === gfortran Summary === # of unexpected failures 1 % setenv MAKE gmake % gmake -j 2 RUNTESTFLAGS="dg.exp=pr71526.f90" check-fortran ... === gfortran Summary === # of expected passes 1 So, the work around is to explicitly set MAKE to gmake before running the testsuite.
