From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B68D33858C66; Tue, 14 Mar 2023 22:36:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B68D33858C66 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678833387; bh=qQ5kv2nQPLd4ymQJPbp/oLDpKL2gtcYoMHCwoQzEtQE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dy+u3jZxWzC0ajukHedGApoXXwzHouXCTAcmldlebUiBUD5ATo+XCID9/Of0HOzaE 5zPowrMiergbLBzORaJrcztTM1DHxIyjvmfQwH3ZjEi+/6zN+RwrqTHFrqEnTukVmp N7208xX2JOn4sBcpvhhbY2wYuRnui6jF4mqoLSzo= From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/109135] Wrong make utility called with LTO testsuite Date: Tue, 14 Mar 2023 22:36: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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109135 --- Comment #3 from Steve Kargl -= -- On Tue, Mar 14, 2023 at 10:25:53PM +0000, pinskia at gcc dot gnu.org wrote: >=20 > --- Comment #1 from Andrew Pinski --- > This is not a testsuite issue but rather the issue is the lto code is cal= ling > make ... >=20 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?=