public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Steve Kargl via Gcc <gcc@gcc.gnu.org>
Cc: sgk@troutmask.apl.washington.edu
Subject: Re: testsuite requires LTO?
Date: Tue, 12 Apr 2022 09:41:47 +0200	[thread overview]
Message-ID: <871qy2oiis.fsf@igel.home> (raw)
In-Reply-To: <YlS/C6QHm7Y4v/Il@troutmask.apl.washington.edu> (Steve Kargl via Gcc's message of "Mon, 11 Apr 2022 16:51:39 -0700")

On Apr 11 2022, Steve Kargl via Gcc wrote:

> Should the testsuite recognize that gcc is built without LTO support?

Yes, we have check_effective_target_lto for that.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

      parent reply	other threads:[~2022-04-12  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 23:51 Steve Kargl
2022-04-12  7:07 ` Richard Biener
2022-04-12  7:26   ` Richard Biener
2022-04-12 17:30     ` Steve Kargl
2022-04-12 17:42       ` Jonathan Wakely
2022-04-12 18:03         ` Steve Kargl
2022-04-12  7:41 ` Andreas Schwab [this message]

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=871qy2oiis.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=gcc@gcc.gnu.org \
    --cc=sgk@troutmask.apl.washington.edu \
    /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).