public inbox for gcc-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-9717] Daily bump. Date: Thu, 22 Jun 2023 00:20:11 +0000 (GMT) [thread overview] Message-ID: <20230622002011.9700C3858C36@sourceware.org> (raw) https://gcc.gnu.org/g:2dfa92f0653771f6872847d1f2629abce21c9158 commit r12-9717-g2dfa92f0653771f6872847d1f2629abce21c9158 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Thu Jun 22 00:19:48 2023 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- libstdc++-v3/ChangeLog | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 047f836b4f3..2fa39115675 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230621 +20230622 diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 214b6013268..bf1868bccd2 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,9 @@ +2023-06-21 Jason Merrill <jason@redhat.com> + + PR tree-optimization/105651 + * include/bits/basic_string.tcc (_M_replace): Add an assert + to avoid -Wrestrict false positive. + 2023-05-30 Alexandre Oliva <oliva@adacore.com> Backported from master:
reply other threads:[~2023-06-22 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=20230622002011.9700C3858C36@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).