From: Jakub Jelinek <jakub@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [committed] testsuite: Uncomment __cpp_consteval test
Date: Thu, 10 Jun 2021 09:48:37 +0200 [thread overview]
Message-ID: <20210610074837.GB7746@tucnak> (raw)
Hi!
The __cpp_consteval macro and corresponding test have been initially
commented out because the consteval support didn't have virtual consteval
method support. The r11-1789-ge6321c4508b2a85c21246c1c06a8208e2a151e48
change enabled the macro but didn't enable the corresponding test.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk as
obvious.
2021-06-10 Jakub Jelinek <jakub@redhat.com>
* g++.dg/cpp2a/feat-cxx2a.C: Uncomment __cpp_consteval test.
* g++.dg/cpp23/feat-cxx2b.C: Likewise.
--- gcc/testsuite/g++.dg/cpp2a/feat-cxx2a.C.jj 2020-11-14 10:40:11.257409305 +0100
+++ gcc/testsuite/g++.dg/cpp2a/feat-cxx2a.C 2021-06-09 15:52:00.827892897 +0200
@@ -520,13 +520,11 @@
# error "__cpp_constexpr_in_decltype != 201711"
#endif
-/* Not supported fully yet:
#ifndef __cpp_consteval
# error "__cpp_consteval"
#elif __cpp_consteval != 201811
# error "__cpp_consteval != 201811"
#endif
-*/
#ifndef __cpp_concepts
# error "__cpp_concepts"
--- gcc/testsuite/g++.dg/cpp23/feat-cxx2b.C.jj 2020-11-14 10:40:11.257409305 +0100
+++ gcc/testsuite/g++.dg/cpp23/feat-cxx2b.C 2021-06-09 15:52:00.827892897 +0200
@@ -520,13 +520,11 @@
# error "__cpp_constexpr_in_decltype != 201711"
#endif
-/* Not supported fully yet:
#ifndef __cpp_consteval
# error "__cpp_consteval"
#elif __cpp_consteval != 201811
# error "__cpp_consteval != 201811"
#endif
-*/
#ifndef __cpp_concepts
# error "__cpp_concepts"
Jakub
reply other threads:[~2021-06-10 7:48 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=20210610074837.GB7746@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).