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++/86419] codecvt<char16_t, ...>::in() and out() incorrectly return ok in some cases.
Date: Fri, 13 Jan 2023 13:44:24 +0000	[thread overview]
Message-ID: <bug-86419-4-pQGS7Jaae3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-86419-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |13.0
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GCC 13. I will consider backporting this to the branches later, as it
doesn't change anything observable by users except for fixing these bugs.

Thanks for the report and the patch.

  parent reply	other threads:[~2023-01-13 13:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-86419-4@http.gcc.gnu.org/bugzilla/>
2020-09-02  0:39 ` dmjpp at hotmail dot com
2020-09-02  0:41 ` dmjpp at hotmail dot com
2020-09-02 16:59 ` redi at gcc dot gnu.org
2020-09-03 16:26 ` dmjpp at hotmail dot com
2020-09-04  8:50 ` dmjpp at hotmail dot com
2020-09-04  8:53 ` dmjpp at hotmail dot com
2020-09-05 21:42 ` dmjpp at hotmail dot com
2020-09-07 15:32 ` redi at gcc dot gnu.org
2020-09-24 14:22 ` dmjpp at hotmail dot com
2020-09-24 14:43 ` redi at gcc dot gnu.org
2023-01-13 13:42 ` cvs-commit at gcc dot gnu.org
2023-01-13 13:44 ` redi at gcc dot gnu.org [this message]
2024-03-18 14:05 ` cvs-commit at gcc dot gnu.org
2024-03-18 14:12 ` 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-86419-4-pQGS7Jaae3@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).