public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-8264] Daily bump.
Date: Wed, 31 Jan 2024 00:24:27 +0000 (GMT) [thread overview]
Message-ID: <20240131002427.473703858C98@sourceware.org> (raw)
https://gcc.gnu.org/g:d87798118f0104053f7df9c3715463a6ace8fc1d
commit r13-8264-gd87798118f0104053f7df9c3715463a6ace8fc1d
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Wed Jan 31 00:24:03 2024 +0000
Daily bump.
Diff:
---
gcc/DATESTAMP | 2 +-
libstdc++-v3/ChangeLog | 41 +++++++++++++++++++++++++++++++++++++++++
2 files changed, 42 insertions(+), 1 deletion(-)
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index d984acab2fc7..e288d0c78f46 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20240130
+20240131
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index fc6ba9b838ac..b2dad84b3545 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,44 @@
+2024-01-30 Jonathan Wakely <jwakely@redhat.com>
+
+ Backported from master:
+ 2024-01-21 Jonathan Wakely <jwakely@redhat.com>
+
+ PR libstdc++/113500
+ * include/bits/chrono_io.h (__formatter_chrono::_M_S): Fix
+ printing of subseconds with floating-point rep.
+ (__formatter_chrono::_M_format_to_ostream): Do not write
+ time_point specializations directly to the ostream.
+ (formatter<chrono::sys_time<D>, C>::parse): Do not allow an
+ empty chrono-spec if the type fails to meet the constraints for
+ writing to an ostream with operator<<.
+ * testsuite/std/time/clock/file/io.cc: Check formatting
+ non-integral times with empty chrono-specs.
+ * testsuite/std/time/clock/gps/io.cc: Likewise.
+ * testsuite/std/time/clock/utc/io.cc: Likewise.
+ * testsuite/std/time/hh_mm_ss/io.cc: Likewise.
+
+2024-01-30 Jonathan Wakely <jwakely@redhat.com>
+
+ Backported from master:
+ 2024-01-21 Jonathan Wakely <jwakely@redhat.com>
+
+ * include/bits/chrono.h (__file_clock::from_sys)
+ (__file_clock::to_sys, __file_clock::_S_from_sys)
+ (__file_clock::_S_to_sys): Use common_type for return type.
+ * testsuite/std/time/clock/file/members.cc: Check round trip
+ conversion for time with lower precision that seconds.
+
+2024-01-30 Jonathan Wakely <jwakely@redhat.com>
+
+ Backported from master:
+ 2024-01-21 Jonathan Wakely <jwakely@redhat.com>
+
+ PR libstdc++/113512
+ * include/std/format (__formatter_fp::format): Fix logic for
+ alternate forms.
+ * testsuite/std/format/functions/format.cc: Check buggy cases of
+ alternate forms with g presentation type.
+
2024-01-18 Jonathan Wakely <jwakely@redhat.com>
Backported from master:
reply other threads:[~2024-01-31 0:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240131002427.473703858C98@sourceware.org \
--to=gccadmin@gcc.gnu.org \
--cc=gcc-cvs@gcc.gnu.org \
--cc=libstdc++-cvs@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).