public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jason Merrill <jason@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-4808] testsuite: constexpr-diag1.C and implicit constexpr Date: Fri, 20 Oct 2023 20:30:40 +0000 (GMT) [thread overview] Message-ID: <20231020203040.2D3C83857C40@sourceware.org> (raw) https://gcc.gnu.org/g:7d4e99131606badcdc343cce62691245dac11bb4 commit r14-4808-g7d4e99131606badcdc343cce62691245dac11bb4 Author: Jason Merrill <jason@redhat.com> Date: Fri Oct 20 15:38:16 2023 -0400 testsuite: constexpr-diag1.C and implicit constexpr This test doesn't break as expected with implicit constexpr. gcc/testsuite/ChangeLog: * g++.dg/cpp1y/constexpr-diag1.C: Add -fno-implicit-constexpr. Diff: --- gcc/testsuite/g++.dg/cpp1y/constexpr-diag1.C | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/g++.dg/cpp1y/constexpr-diag1.C b/gcc/testsuite/g++.dg/cpp1y/constexpr-diag1.C index 0e2909e83ef6..e12633ca0852 100644 --- a/gcc/testsuite/g++.dg/cpp1y/constexpr-diag1.C +++ b/gcc/testsuite/g++.dg/cpp1y/constexpr-diag1.C @@ -1,6 +1,6 @@ // PR c++/111272 // { dg-do compile { target c++14 } } -// { dg-options "-Werror=invalid-constexpr" } +// { dg-options "-Werror=invalid-constexpr -fno-implicit-constexpr" } // { dg-prune-output "some warnings being treated as errors" } struct Jam
reply other threads:[~2023-10-20 20:30 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=20231020203040.2D3C83857C40@sourceware.org \ --to=jason@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).