public inbox for libstdc++-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 r13-1151] libstdc++: Add missing #include <string> to new test
Date: Fri, 17 Jun 2022 12:30:43 +0000 (GMT)	[thread overview]
Message-ID: <20220617123043.479B0385742F@sourceware.org> (raw)

https://gcc.gnu.org/g:0f96ac43fa0a5fdbfce317b274233852d5b46d23

commit r13-1151-g0f96ac43fa0a5fdbfce317b274233852d5b46d23
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Jun 17 13:29:05 2022 +0100

    libstdc++: Add missing #include <string> to new test
    
    Somehow I pushed a different version of this test to the one I actually
    tested.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/21_strings/basic_string/cons/char/105995.cc: Add
            missing #include.

Diff:
---
 libstdc++-v3/testsuite/21_strings/basic_string/cons/char/105995.cc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libstdc++-v3/testsuite/21_strings/basic_string/cons/char/105995.cc b/libstdc++-v3/testsuite/21_strings/basic_string/cons/char/105995.cc
index aa8bcba3dca..4764ceff72a 100644
--- a/libstdc++-v3/testsuite/21_strings/basic_string/cons/char/105995.cc
+++ b/libstdc++-v3/testsuite/21_strings/basic_string/cons/char/105995.cc
@@ -2,6 +2,8 @@
 // { dg-do compile { target c++20 } }
 // { dg-require-effective-target cxx11_abi }
 
+#include <string>
+
 // PR libstdc++/105995
 // Not required by the standard, but supported for QoI.
 constexpr std::string pr105995_empty;


                 reply	other threads:[~2022-06-17 12: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=20220617123043.479B0385742F@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).