public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: David Edelsohn <dje@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-1495] testsuite: Require LTO for pr107557-[12].c Date: Fri, 2 Jun 2023 13:26:08 +0000 (GMT) [thread overview] Message-ID: <20230602132608.DEBCA3858D32@sourceware.org> (raw) https://gcc.gnu.org/g:23f352972faabe94606687558a66135f9a9e17fb commit r14-1495-g23f352972faabe94606687558a66135f9a9e17fb Author: David Edelsohn <dje.gcc@gmail.com> Date: Thu Jun 1 15:16:27 2023 -0400 testsuite: Require LTO for pr107557-[12].c pr107557-[12].c invoke -flto option but do not check that the target support LTO. This patch adds dg-require lto to the testcases. * gcc.dg/pr107557-1.c: Require LTO support. * gcc.dg/pr107557-2.c: Require LTO support. Signed-off-by: David Edelsohn <dje.gcc@gmail.com> Diff: --- gcc/testsuite/gcc.dg/pr107557-1.c | 1 + gcc/testsuite/gcc.dg/pr107557-2.c | 1 + 2 files changed, 2 insertions(+) diff --git a/gcc/testsuite/gcc.dg/pr107557-1.c b/gcc/testsuite/gcc.dg/pr107557-1.c index 88c248b6564..f14b784dbbf 100644 --- a/gcc/testsuite/gcc.dg/pr107557-1.c +++ b/gcc/testsuite/gcc.dg/pr107557-1.c @@ -1,5 +1,6 @@ /* PR107557 * { dg-do compile } + * { dg-require-effective-target lto } * { dg-options "-flto -fsanitize=undefined -fexceptions -Wno-incompatible-pointer-types" } */ diff --git a/gcc/testsuite/gcc.dg/pr107557-2.c b/gcc/testsuite/gcc.dg/pr107557-2.c index 2d26bb0b16a..e680d045165 100644 --- a/gcc/testsuite/gcc.dg/pr107557-2.c +++ b/gcc/testsuite/gcc.dg/pr107557-2.c @@ -1,5 +1,6 @@ /* PR107557 * { dg-do compile } + * { dg-require-effective-target lto } * { dg-options "-flto -fsanitize=undefined -fexceptions -Wno-incompatible-pointer-types" } */
reply other threads:[~2023-06-02 13:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230602132608.DEBCA3858D32@sourceware.org \ --to=dje@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).