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 r14-2274] libstdc++: Fix <iosfwd> synopsis test
Date: Mon,  3 Jul 2023 23:08:13 +0000 (GMT)	[thread overview]
Message-ID: <20230703230813.29ED43857025@sourceware.org> (raw)

https://gcc.gnu.org/g:f9f05e483984bf89fec7778aaa55ece8ba2a86bb

commit r14-2274-gf9f05e483984bf89fec7778aaa55ece8ba2a86bb
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Jul 3 19:33:18 2023 +0100

    libstdc++: Fix <iosfwd> synopsis test
    
    The <syncstream> header is only supported for the cxx11 ABI. The
    declarations of basic_syncbuf, basic_osyncstream, syncbuf and
    osyncstream were already correctly guarded by a check for
    _GLIBCXX_USE_CXX11_ABI, but the wsyncbuf and wosyncstream declarations
    were not.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/27_io/headers/iosfwd/synopsis.cc: Make wsyncbuf and
            wosyncstream depend on _GLIBCXX_USE_CXX11_ABI.

Diff:
---
 libstdc++-v3/testsuite/27_io/headers/iosfwd/synopsis.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/27_io/headers/iosfwd/synopsis.cc b/libstdc++-v3/testsuite/27_io/headers/iosfwd/synopsis.cc
index b6d3fa7a719..12f47ae8133 100644
--- a/libstdc++-v3/testsuite/27_io/headers/iosfwd/synopsis.cc
+++ b/libstdc++-v3/testsuite/27_io/headers/iosfwd/synopsis.cc
@@ -115,7 +115,7 @@ _GLIBCXX_END_NAMESPACE_CXX11
   typedef basic_ofstream<wchar_t> wofstream;
   typedef basic_fstream<wchar_t>  wfstream;
 
-#if __cplusplus >= 202002L
+#if __cplusplus >= 202002L && _GLIBCXX_USE_CXX11_ABI
   typedef basic_syncbuf<wchar_t>     wsyncbuf;
   typedef basic_osyncstream<wchar_t> wosyncstream;
 #endif

                 reply	other threads:[~2023-07-03 23:08 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=20230703230813.29ED43857025@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).