public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] c++: testsuite: require lto_incremental in pr90990_0.C Date: Tue, 21 Jun 2022 00:16:28 +0000 (GMT) [thread overview] Message-ID: <20220621001628.CCA743841465@sourceware.org> (raw) https://gcc.gnu.org/g:c9f96bc66f73551edc01ff513ab43f2e20e23c20 commit c9f96bc66f73551edc01ff513ab43f2e20e23c20 Author: Alexandre Oliva <oliva@adacore.com> Date: Mon Jun 20 19:44:27 2022 -0300 c++: testsuite: require lto_incremental in pr90990_0.C Other LTO tests that use -r require the lto_incremental effective target. I suppose pr90990_0.C is missing it due to an oversight. This patch arranges for this test to also be skipped on non-lto_incremental targets. for gcc/testsuite/ChangeLog * g++.dg/lto/pr90990_0.C: Require lto_incremental target. Diff: --- gcc/testsuite/g++.dg/lto/pr90990_0.C | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/g++.dg/lto/pr90990_0.C b/gcc/testsuite/g++.dg/lto/pr90990_0.C index 22a5e3ffaaa..74cc2bbd928 100644 --- a/gcc/testsuite/g++.dg/lto/pr90990_0.C +++ b/gcc/testsuite/g++.dg/lto/pr90990_0.C @@ -1,5 +1,6 @@ // { dg-lto-do link } /* { dg-extra-ld-options { -r -nostdlib } } */ +// { dg-require-effective-target lto_incremental } class A { public: float m_floats;
next reply other threads:[~2022-06-21 0:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-21 0:16 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-06-22 0:44 Alexandre Oliva 2022-06-21 0:08 Alexandre Oliva
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=20220621001628.CCA743841465@sourceware.org \ --to=aoliva@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).