public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-3982] testsuite: Skip a test-case when LTO is used [PR102509] Date: Thu, 30 Sep 2021 12:17:19 +0000 (GMT) [thread overview] Message-ID: <20210930121719.EF5A03857C65@sourceware.org> (raw) https://gcc.gnu.org/g:c3d11a1e9528b6140c65a66d47225a0b6a8814e0 commit r12-3982-gc3d11a1e9528b6140c65a66d47225a0b6a8814e0 Author: Martin Liska <mliska@suse.cz> Date: Thu Sep 30 14:12:35 2021 +0200 testsuite: Skip a test-case when LTO is used [PR102509] PR testsuite/102509 gcc/testsuite/ChangeLog: * gcc.c-torture/compile/attr-complex-method.c: Skip if LTO is used. * gcc.c-torture/compile/attr-complex-method-2.c: Likewise. Diff: --- gcc/testsuite/gcc.c-torture/compile/attr-complex-method-2.c | 1 + gcc/testsuite/gcc.c-torture/compile/attr-complex-method.c | 1 + 2 files changed, 2 insertions(+) diff --git a/gcc/testsuite/gcc.c-torture/compile/attr-complex-method-2.c b/gcc/testsuite/gcc.c-torture/compile/attr-complex-method-2.c index a3dc9c1ba91..121ae17f64b 100644 --- a/gcc/testsuite/gcc.c-torture/compile/attr-complex-method-2.c +++ b/gcc/testsuite/gcc.c-torture/compile/attr-complex-method-2.c @@ -1,4 +1,5 @@ /* { dg-additional-options "-fcx-limited-range -fdump-tree-optimized" } */ +/* { dg-skip-if "" { *-*-* } { "-flto" } { "" } } */ #pragma GCC optimize "-fno-cx-limited-range" diff --git a/gcc/testsuite/gcc.c-torture/compile/attr-complex-method.c b/gcc/testsuite/gcc.c-torture/compile/attr-complex-method.c index f08b72e273f..046de7efeb9 100644 --- a/gcc/testsuite/gcc.c-torture/compile/attr-complex-method.c +++ b/gcc/testsuite/gcc.c-torture/compile/attr-complex-method.c @@ -1,4 +1,5 @@ /* { dg-additional-options "-fdump-tree-optimized" } */ +/* { dg-skip-if "" { *-*-* } { "-flto" } { "" } } */ #pragma GCC optimize "-fcx-limited-range"
reply other threads:[~2021-09-30 12:17 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=20210930121719.EF5A03857C65@sourceware.org \ --to=marxin@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).