From: Jason Merrill <jason@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [pushed] testsuite: std_list handling for { target c++26 }
Date: Tue, 27 Jun 2023 23:28:58 -0400 [thread overview]
Message-ID: <20230628032858.2614753-1-jason@redhat.com> (raw)
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
As with c++23, we want to run { target c++26 } tests even though it isn't
part of the default std_list.
C++17 with Concepts TS is no longer an interesting target configuration.
And bump the impcx target to use C++26 mode instead of 23.
gcc/testsuite/ChangeLog:
* lib/g++-dg.exp (g++-dg-runtest): Update for C++26.
---
gcc/testsuite/lib/g++-dg.exp | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/gcc/testsuite/lib/g++-dg.exp b/gcc/testsuite/lib/g++-dg.exp
index 08185a8987e..046d63170c8 100644
--- a/gcc/testsuite/lib/g++-dg.exp
+++ b/gcc/testsuite/lib/g++-dg.exp
@@ -58,17 +58,17 @@ proc g++-dg-runtest { testcases flags default-extra-flags } {
# single test. This should be updated or commented
# out whenever the default std_list is updated or newer
# C++ effective target is added.
- if [search_for $test "{ dg-do * { target c++23 } }"] {
- set std_list { 23 }
+ if [search_for $test "\{ dg-do * \{ target c++23"] {
+ set std_list { 23 26 }
+ } elseif [search_for $test "\{ dg-do * \{ target c++26"] {
+ set std_list { 26 }
} else {
set std_list { 98 14 17 20 }
}
}
set option_list { }
foreach x $std_list {
- # Handle "concepts" as C++17 plus Concepts TS.
- if { $x eq "concepts" } then { set x "17 -fconcepts"
- } elseif { $x eq "impcx" } then { set x "23 -fimplicit-constexpr" }
+ if { $x eq "impcx" } then { set x "26 -fimplicit-constexpr" }
lappend option_list "${std_prefix}$x"
}
} else {
base-commit: ebe7c586f62b1c5218b19c3c6853163287b3c887
--
2.39.3
reply other threads:[~2023-06-28 3:29 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=20230628032858.2614753-1-jason@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@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: 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).