public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r14-4050] libstdc++: Remove dg-options "-std=c++20" from <span> and <cuchar> tests
Date: Fri, 15 Sep 2023 23:03:57 +0000 (GMT)	[thread overview]
Message-ID: <20230915230357.8E46A3856DD6@sourceware.org> (raw)

https://gcc.gnu.org/g:5d066729ff0b9c9a2aae975244bb96f8e55e7d08

commit r14-4050-g5d066729ff0b9c9a2aae975244bb96f8e55e7d08
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Sep 4 16:01:16 2023 +0100

    libstdc++: Remove dg-options "-std=c++20" from <span> and <cuchar> tests
    
    The testsuite will automatically select C++20 for these tests now, and
    removing the hardcoded -std option allows them to be tested for C++23
    and C++26 as well.
    
    There doesn't seem to be any reason they need to use strict -std=c++20
    mode, so don't add the { dg-add-options strict_std } directive, just let
    them use strict or non-strict modes.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/21_strings/headers/cuchar/functions_std_cxx20.cc:
            Remove dg-options.
            * testsuite/23_containers/span/contiguous_range_neg.cc:
            Likewise.
            * testsuite/23_containers/span/everything.cc: Likewise.

Diff:
---
 .../testsuite/21_strings/headers/cuchar/functions_std_cxx20.cc         | 1 -
 libstdc++-v3/testsuite/23_containers/span/contiguous_range_neg.cc      | 3 +--
 libstdc++-v3/testsuite/23_containers/span/everything.cc                | 3 +--
 3 files changed, 2 insertions(+), 5 deletions(-)

diff --git a/libstdc++-v3/testsuite/21_strings/headers/cuchar/functions_std_cxx20.cc b/libstdc++-v3/testsuite/21_strings/headers/cuchar/functions_std_cxx20.cc
index df68fb7c82f..1964803cbd1 100644
--- a/libstdc++-v3/testsuite/21_strings/headers/cuchar/functions_std_cxx20.cc
+++ b/libstdc++-v3/testsuite/21_strings/headers/cuchar/functions_std_cxx20.cc
@@ -1,4 +1,3 @@
-// { dg-options "-std=c++20" }
 // { dg-do compile { target c++20 } }
 
 #include <cuchar>
diff --git a/libstdc++-v3/testsuite/23_containers/span/contiguous_range_neg.cc b/libstdc++-v3/testsuite/23_containers/span/contiguous_range_neg.cc
index d5f64922052..2ed44740a86 100644
--- a/libstdc++-v3/testsuite/23_containers/span/contiguous_range_neg.cc
+++ b/libstdc++-v3/testsuite/23_containers/span/contiguous_range_neg.cc
@@ -15,8 +15,7 @@
 // with this library; see the file COPYING3.  If not see
 // <http://www.gnu.org/licenses/>.
 
-// { dg-options "-std=c++2a" }
-// { dg-do compile { target c++2a } }
+// { dg-do compile { target c++20 } }
 
 #include <span>
 #include <deque>
diff --git a/libstdc++-v3/testsuite/23_containers/span/everything.cc b/libstdc++-v3/testsuite/23_containers/span/everything.cc
index 74f943e937f..31c17346dd3 100644
--- a/libstdc++-v3/testsuite/23_containers/span/everything.cc
+++ b/libstdc++-v3/testsuite/23_containers/span/everything.cc
@@ -15,8 +15,7 @@
 // with this library; see the file COPYING3.  If not see
 // <http://www.gnu.org/licenses/>.
 
-// { dg-options "-std=c++2a" }
-// { dg-do run { target c++2a } }
+// { dg-do run { target c++20 } }
 
 #include <testsuite_hooks.h>

                 reply	other threads:[~2023-09-15 23:03 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=20230915230357.8E46A3856DD6@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-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: 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).