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++/112607] <format>: _Normalize does not consider char_type for the basic_string_view case
Date: Tue, 28 Nov 2023 22:30:25 +0000	[thread overview]
Message-ID: <bug-112607-4-IdzL5Valhy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112607-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from GCC 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:c7c92d61d32f6fd7746e2844f68d1936e2b6f6f6

commit r13-8105-gc7c92d61d32f6fd7746e2844f68d1936e2b6f6f6
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Sat Nov 18 20:56:35 2023 +0000

    libstdc++: Check string value_type in std::make_format_args [PR112607]

    libstdc++-v3/ChangeLog:

            PR libstdc++/112607
            * include/std/format (basic_format_arg::_S_to_arg_type): Check
            value_type for basic_string_view and basic_string
            specializations.
            * testsuite/std/format/arguments/112607.cc: New test.

    (cherry picked from commit 279e407a06cc676d8e6e0bb5755b0a804e05377c)

  parent reply	other threads:[~2023-11-28 22:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18 16:28 [Bug libstdc++/112607] New: " hewillk at gmail dot com
2023-11-18 18:09 ` [Bug libstdc++/112607] " redi at gcc dot gnu.org
2023-11-18 18:15 ` redi at gcc dot gnu.org
2023-11-18 18:20 ` redi at gcc dot gnu.org
2023-11-18 19:42 ` redi at gcc dot gnu.org
2023-11-18 21:44 ` cvs-commit at gcc dot gnu.org
2023-11-18 21:52 ` redi at gcc dot gnu.org
2023-11-28 22:30 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-28 22:32 ` 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-112607-4-IdzL5Valhy@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).