public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth 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: Wed, 26 Apr 2023 06:57:57 +0000 [thread overview] Message-ID: <bug-108969-4-5R9mNlyVIc@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|13.0 |13.2 --- Comment #25 from Richard Biener <rguenth at gcc dot gnu.org> --- GCC 13.1 is being released, retargeting bugs to GCC 13.2.
next prev parent reply other threads:[~2023-04-26 6:57 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 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 [this message] 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-5R9mNlyVIc@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: linkBe 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).