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 r12-9371] Daily bump. Date: Fri, 31 Mar 2023 00:20:56 +0000 (GMT) [thread overview] Message-ID: <20230331002056.CA2D03858D35@sourceware.org> (raw) https://gcc.gnu.org/g:efa5d940aca937fbe5a4469ef46714047a335ba5 commit r12-9371-gefa5d940aca937fbe5a4469ef46714047a335ba5 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Mar 31 00:20:15 2023 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 6 ++++++ libstdc++-v3/ChangeLog | 9 +++++++++ 3 files changed, 16 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 6800443be95..bc28fe8762d 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230330 +20230331 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 51183083c2a..ca6f4db4c36 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,9 @@ +2023-03-30 Andrew Pinski <apinski@marvell.com> + + * dump-parse-tree.cc (get_c_type_name): Fix "long_long" + type name to be "long long". Add a comment on why adding + 2 to the name too. + 2023-03-27 Harald Anlauf <anlauf@gmx.de> Backported from master: diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 3f20e2ca8f8..7013ebcad0c 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,12 @@ +2023-03-30 Jonathan Wakely <jwakely@redhat.com> + + Backported from master: + 2023-03-29 Jonathan Wakely <jwakely@redhat.com> + + PR libstdc++/109242 + * include/std/optional (transform): Use std::remove_cv_t. + * testsuite/20_util/optional/monadic/pr109242.cc: New test. + 2023-03-28 Jonathan Wakely <jwakely@redhat.com> Backported from master:
reply other threads:[~2023-03-31 0:20 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=20230331002056.CA2D03858D35@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: linkBe 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).