public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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 22:36:27 +0000	[thread overview]
Message-ID: <bug-109135-4-2CK475VccB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109135-4@http.gcc.gnu.org/bugzilla/>

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?

  parent reply	other threads:[~2023-03-14 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 22:23 [Bug testsuite/109135] New: " kargl at gcc dot gnu.org
2023-03-14 22:25 ` [Bug driver/109135] " pinskia at gcc dot gnu.org
2023-03-14 22:30 ` pinskia at gcc dot gnu.org
2023-03-14 22:36 ` sgk at troutmask dot apl.washington.edu [this message]
2023-03-14 23:06 ` sgk at troutmask dot apl.washington.edu
2023-03-14 23:14 ` sgk at troutmask dot apl.washington.edu
2023-03-15  8:35 ` rguenth at gcc dot gnu.org
2023-03-15 14:33 ` sgk at troutmask dot apl.washington.edu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109135-4-2CK475VccB@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).