public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108969] [13/14 Regression] Initializing iostreams in the library needs a GLIBCXX_3.4.31 versioned symbol
Date: Tue, 18 Apr 2023 16:00:02 +0000	[thread overview]
Message-ID: <bug-108969-4-0bRWrm4QgN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108969-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108969

--- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:

https://gcc.gnu.org/g:762be0646bf96761ce68a9e06ab60c453e0963d0

commit r13-7217-g762be0646bf96761ce68a9e06ab60c453e0963d0
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Apr 18 14:37:38 2023 +0100

    libstdc++: Export global iostreams with GLIBCXX_3.4.31 symver [PR108969]

    Since GCC 13 the global iostream objects are only initialized once in
    libstdc++, and not by a std::ios::Init object in every translation unit
    that includes <iostream>. To avoid using uninitialized streams defined
    in an older libstdc++.so, translation units using the global iostreams
    should depend on the GLIBCXX_3.4.31 symver.

    Define std::cin as std::__io::cin and then export it as
    std::cin@@GLIBCXX_3.4.31 so that references to std::cin bind to the new
    symver. Also export it as @GLIBCXX_3.4 for backwards compatibility

    libstdc++-v3/ChangeLog:

            PR libstdc++/108969
            * src/Makefile.am: Move globals_io.cc to here.
            * src/Makefile.in: Regenerate.
            * src/c++98/Makefile.am: Remove globals_io.cc from here.
            * src/c++98/Makefile.in: Regenerate.
            * src/c++98/globals_io.cc [_GLIBCXX_SYMVER_GNU] (cin): Adjust
            symbol name and then export with GLIBCXX_3.4.31 symver.
            (cout, cerr, clog, wcin, wcout, wcerr, wclog): Likewise.
            * config/abi/post/aarch64-linux-gnu/baseline_symbols.txt:
            Regenerate.
            * config/abi/post/i486-linux-gnu/baseline_symbols.txt:
            Regenerate.
            * config/abi/post/m68k-linux-gnu/baseline_symbols.txt:
            Regenerate.
            * config/abi/post/powerpc64-linux-gnu/baseline_symbols.txt:
            Regenerate.
            * config/abi/post/riscv64-linux-gnu/baseline_symbols.txt:
            Regenerate.
            * config/abi/post/x86_64-linux-gnu/32/baseline_symbols.txt:
            Regenerate.
            * config/abi/post/s390x-linux-gnu/baseline_symbols.txt:
            Regenerate.
            * config/abi/post/x86_64-linux-gnu/baseline_symbols.txt:
            Regenerate.
            * config/abi/pre/gnu.ver: Add iostream objects to new symver.

  parent reply	other threads:[~2023-04-18 16:00 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 13:08 [Bug libstdc++/108969] New: [13 " redi at gcc dot gnu.org
2023-02-28 13:09 ` [Bug libstdc++/108969] " redi at gcc dot gnu.org
2023-02-28 13:21 ` jakub at gcc dot gnu.org
2023-02-28 13:22 ` redi at gcc dot gnu.org
2023-02-28 13:25 ` jakub at gcc dot gnu.org
2023-02-28 13:28 ` redi at gcc dot gnu.org
2023-02-28 13:30 ` jakub at gcc dot gnu.org
2023-02-28 13:34 ` fw at gcc dot gnu.org
2023-02-28 13:36 ` redi at gcc dot gnu.org
2023-02-28 13:51 ` jakub at gcc dot gnu.org
2023-02-28 13:54 ` rguenth at gcc dot gnu.org
2023-02-28 14:09 ` redi at gcc dot gnu.org
2023-03-03 17:25 ` ppalka at gcc dot gnu.org
2023-03-08  9:20 ` rguenth at gcc dot gnu.org
2023-03-08  9:28 ` jakub at gcc dot gnu.org
2023-03-27 10:55 ` rguenth at gcc dot gnu.org
2023-04-18 15:58 ` [Bug libstdc++/108969] [13/14 " cvs-commit at gcc dot gnu.org
2023-04-18 16:00 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-18 16:00 ` redi at gcc dot gnu.org
2023-04-18 16:31 ` cvs-commit at gcc dot gnu.org
2023-04-18 16:31 ` cvs-commit at gcc dot gnu.org
2023-04-19 14:17 ` jakub at gcc dot gnu.org
2023-04-19 14:17 ` sjames at gcc dot gnu.org
2023-04-19 14:25 ` jakub at gcc dot gnu.org
2023-04-19 14:45 ` fw at gcc dot gnu.org
2023-04-19 14:48 ` jakub at gcc dot gnu.org
2023-04-26  6:57 ` rguenth at gcc dot gnu.org
2023-04-26 18:15 ` xry111 at gcc dot gnu.org
2023-04-28  8:50 ` cvs-commit at gcc dot gnu.org
2023-04-28 20:57 ` romain.geissler at amadeus dot com
2023-04-28 20:58 ` romain.geissler at amadeus dot com
2023-04-28 21:16 ` redi at gcc dot gnu.org
2023-04-28 21:21 ` romain.geissler at amadeus dot com
2023-05-04  7:44 ` cvs-commit at gcc dot gnu.org
2023-05-04  7:49 ` jakub at gcc dot gnu.org

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=bug-108969-4-0bRWrm4QgN@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).