From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id B88593858D39; Tue, 14 Mar 2023 23:14:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B88593858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678835667;
	bh=GGr6AttdIK7lBoaRPvP6hEzt7RrFZieqzrytJUQMwbE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=LdoSdB0C7R4jVFBZxnBHbHSsE+leYtQyPOKAGsk387RvvMbcWpd0eEeJXfuipb+Op
	 wW9m6lNYC2uVfaNbA/pBVieB+1XOxCDUqd+IK4BQ5vKSbCbsmsdNEc6JrSoRKP5n9W
	 QgdwXGqjQAR4/3DdhkQ3/+UmAYb4PQYgGUNTrU3o=
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/109135] Wrong make utility called with LTO testsuite
Date: Tue, 14 Mar 2023 23:14:27 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109135-4-IucpludrQD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109135-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109135-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109135

--- 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=3D109135
>=20
> --- 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 wrot=
e:
> >=20
> > --- 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 c=
alling
> > make ...
> >=20
>=20
> That explains why groping around in gcc/testsuite for
> a rogue make or MAKE was coming up empty.
>=20
> 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?
>=20

Answered my own question.

% gmake RUNTESTFLAGS=3D"dg.exp=3Dpr71526.f90" check-fortran
...
                =3D=3D=3D gfortran Summary =3D=3D=3D

# of expected passes            1

% gmake -j 1 RUNTESTFLAGS=3D"dg.exp=3Dpr71526.f90" check-fortran
...
                =3D=3D=3D gfortran Summary =3D=3D=3D

# of expected passes            1

% gmake -j 2 RUNTESTFLAGS=3D"dg.exp=3Dpr71526.f90" check-fortran
...
FAIL: gfortran.dg/pr71526.f90   -O  (test for excess errors)

                =3D=3D=3D gfortran Summary =3D=3D=3D

# of unexpected failures        1

% setenv MAKE gmake
% gmake -j 2 RUNTESTFLAGS=3D"dg.exp=3Dpr71526.f90" check-fortran
...
                =3D=3D=3D gfortran Summary =3D=3D=3D

# of expected passes            1

So, the work around is to explicitly set MAKE to gmake before
running the testsuite.=