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++/110708] std::format("{:%EEC %OOd}", std::chrono::system_clock::now()) should be rejected
Date: Fri, 28 Jul 2023 17:32:42 +0000	[thread overview]
Message-ID: <bug-110708-4-mVmHfb9grL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110708-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:74f1c016f44daf18e4bed76b283cd5bfd0b5c8c7

commit r13-7629-g74f1c016f44daf18e4bed76b283cd5bfd0b5c8c7
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Jul 18 10:36:37 2023 +0100

    libstdc++: Check for multiple modifiers in chrono format string [PR110708]

    The logic for handling modified chrono specs like %Ey was just
    restarting the loop after each modifier, and not checking whether we'd
    already seen a modifier.

    libstdc++-v3/ChangeLog:

            PR libstdc++/110708
            * include/bits/chrono_io.h (__formatter_chrono::_M_parse): Only
            allow a single modifier.
            * testsuite/std/time/format.cc: Check multiple modifiers.

    (cherry picked from commit 52bfec7ea0eb0f1a4c5bfa55b0d6b9b6c8808e26)

  parent reply	other threads:[~2023-07-28 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 20:46 [Bug libstdc++/110708] New: " redi at gcc dot gnu.org
2023-07-17 20:47 ` [Bug libstdc++/110708] " redi at gcc dot gnu.org
2023-07-18 11:28 ` redi at gcc dot gnu.org
2023-07-19 10:11 ` cvs-commit at gcc dot gnu.org
2023-07-19 10:13 ` redi at gcc dot gnu.org
2023-07-28 17:32 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-28 19:00 ` 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-110708-4-mVmHfb9grL@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).