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 r11-9918] libstdc++: Ensure C++20 std::stringstream definitions use correct ABI
Date: Thu, 21 Apr 2022 12:34:00 +0000 (GMT)	[thread overview]
Message-ID: <20220421123400.1B31D3888C4F@sourceware.org> (raw)

https://gcc.gnu.org/g:615cc91a99aaac737739644639dd9a27b1404b4a

commit r11-9918-g615cc91a99aaac737739644639dd9a27b1404b4a
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Nov 30 22:04:49 2021 +0000

    libstdc++: Ensure C++20 std::stringstream definitions use correct ABI
    
    The definitions of the new C++20 members of std::stringstream etc are
    missing when --with-default-libstdcxx-abi=gcc4-compatible is used,
    because all the explicit instantiations in src/c++20/sstream-inst.cc are
    skipped.
    
    This ensures the contents of that file are compiled with the new ABI, so
    the same set of symbols are exported regardless of which ABI is active
    by default.
    
    libstdc++-v3/ChangeLog:
    
            * src/c++20/sstream-inst.cc (_GLIBCXX_USE_CXX11_ABI): Define to
            select new ABI.
    
    (cherry picked from commit 56b07badf052fb140c4636f6d77cfc02d1ac357c)

Diff:
---
 libstdc++-v3/src/c++20/sstream-inst.cc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/src/c++20/sstream-inst.cc b/libstdc++-v3/src/c++20/sstream-inst.cc
index b3fbd6ead44..55d1fe5234d 100644
--- a/libstdc++-v3/src/c++20/sstream-inst.cc
+++ b/libstdc++-v3/src/c++20/sstream-inst.cc
@@ -26,7 +26,9 @@
 // ISO C++ 14882:
 //
 
-// Instantiations in this file are only for the new SSO std::string ABI
+// Instantiations in this file are only for the new SSO std::string ABI.
+#define _GLIBCXX_USE_CXX11_ABI 1
+
 #include <sstream>
 
 #if _GLIBCXX_USE_CXX11_ABI


                 reply	other threads:[~2022-04-21 12:34 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=20220421123400.1B31D3888C4F@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).