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++/110719] Should chrono formatters always use std::time_put for locale's representation?
Date: Fri, 28 Jul 2023 17:32:53 +0000 [thread overview]
Message-ID: <bug-110719-4-OTlXHVRfWy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110719-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110719
--- Comment #6 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:24c352c41eb944d29b09f33a42662efad3f6f811
commit r13-7631-g24c352c41eb944d29b09f33a42662efad3f6f811
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Jul 19 14:38:08 2023 +0100
libstdc++: Fix locale-specific duration formatting [PR110719]
The r14-2640-gf4bce119f617dc commit only removed fractional seconds for
time points, but it needs to be done for durations and hh_mm_ss types
too.
libstdc++-v3/ChangeLog:
PR libstdc++/110719
* include/bits/chrono_io.h (__formatter_chrono::_S_floor_seconds):
Handle duration and hh_mm_ss.
* testsuite/20_util/duration/io.cc: Check locale-specific
formats.
* testsuite/std/time/hh_mm_ss/io.cc: Likewise.
(cherry picked from commit 86b36e9f7e3839e923db2fda4962cd3faf2ea47b)
next prev parent reply other threads:[~2023-07-28 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 14:43 [Bug libstdc++/110719] New: " redi at gcc dot gnu.org
2023-07-19 10:13 ` [Bug libstdc++/110719] " redi at gcc dot gnu.org
2023-07-19 10:37 ` redi at gcc dot gnu.org
2023-07-19 11:37 ` cvs-commit at gcc dot gnu.org
2023-07-19 11:39 ` redi at gcc dot gnu.org
2023-07-19 15:51 ` cvs-commit at gcc dot gnu.org
2023-07-28 17:32 ` cvs-commit at gcc dot gnu.org
2023-07-28 17:32 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-28 18:59 ` 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-110719-4-OTlXHVRfWy@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).