public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/59675] -D_GLIBCXX_DEBUG asserts to stdout (it should stderr)
Date: Wed, 03 Nov 2021 16:08:05 +0000	[thread overview]
Message-ID: <bug-59675-4-CgO6R8Q90A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59675-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |12.0
           Keywords|                            |patch

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Patch available now:
https://gcc.gnu.org/pipermail/gcc-patches/2021-October/582682.html

  parent reply	other threads:[~2021-11-03 16:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-04 12:14 [Bug c++/59675] New: " jan.kratochvil at redhat dot com
2014-01-15  8:32 ` [Bug libstdc++/59675] " jan.kratochvil at redhat dot com
2014-01-15  8:35 ` jakub at gcc dot gnu.org
2014-01-15  9:01 ` redi at gcc dot gnu.org
2015-05-06 15:43 ` jan.kratochvil at redhat dot com
2015-05-06 16:09 ` redi at gcc dot gnu.org
2020-03-08 17:36 ` jan.kratochvil at redhat dot com
2021-10-18  8:43 ` yfeldblum at gmail dot com
2021-10-18 10:37 ` redi at gcc dot gnu.org
2021-11-03 16:08 ` redi at gcc dot gnu.org [this message]
2021-11-12 12:25 ` cvs-commit at gcc dot gnu.org
2021-11-12 12:26 ` redi 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-59675-4-CgO6R8Q90A@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).