From: Jason Merrill <jason@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [pushed] testsuite: run C++11 tests in C++11 mode
Date: Tue, 25 Jul 2023 21:44:23 -0400 [thread overview]
Message-ID: <20230726014423.2747726-1-jason@redhat.com> (raw)
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
A recent change missed updating constexpr-mutable3.C because it wasn't run
in C++11 mode even though it checks the behavior for { target c++11_only }.
gcc/testsuite/ChangeLog:
* lib/g++-dg.exp (g++-dg-runtest): Check for c++11_only.
---
gcc/testsuite/lib/g++-dg.exp | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/gcc/testsuite/lib/g++-dg.exp b/gcc/testsuite/lib/g++-dg.exp
index 046d63170c8..142c52c8426 100644
--- a/gcc/testsuite/lib/g++-dg.exp
+++ b/gcc/testsuite/lib/g++-dg.exp
@@ -55,13 +55,16 @@ proc g++-dg-runtest { testcases flags default-extra-flags } {
} else {
# If the test requires a newer C++ version than which
# is tested by default, use that C++ version for that
- # single test. This should be updated or commented
- # out whenever the default std_list is updated or newer
- # C++ effective target is added.
+ # single test. Or if a test checks behavior specifically for
+ # one C++ version, include that version in the default list.
+ # These should be adjusted 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 26 }
} elseif [search_for $test "\{ dg-do * \{ target c++26"] {
set std_list { 26 }
+ } elseif [search_for $test "c++11_only"] {
+ set std_list { 98 11 14 20 }
} else {
set std_list { 98 14 17 20 }
}
base-commit: 50656980497d77ac12a5e7179013a6af09ba32f7
--
2.39.3
reply other threads:[~2023-07-26 1:44 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=20230726014423.2747726-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).