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 r11-10498] Daily bump. Date: Fri, 3 Feb 2023 00:20:04 +0000 (GMT) [thread overview] Message-ID: <20230203002004.E08143858C5F@sourceware.org> (raw) https://gcc.gnu.org/g:fc9837d4a7051162ce1d69dd5e21c9cfe4db1c2e commit r11-10498-gfc9837d4a7051162ce1d69dd5e21c9cfe4db1c2e Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Feb 3 00:19:24 2023 +0000 Daily bump. Diff: --- gcc/ChangeLog | 9 +++++++++ gcc/DATESTAMP | 2 +- libstdc++-v3/ChangeLog | 9 +++++++++ 3 files changed, 19 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 9b7391510f0..71e2e4b509e 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,12 @@ +2023-02-02 Martin Jambor <mjambor@suse.cz> + + Backported from master: + 2023-01-18 Martin Jambor <mjambor@suse.cz> + + PR ipa/107944 + * cgraph.c (cgraph_node::remove): Check whether nodes up the + lcone_of chain also do not need the body. + 2023-01-26 Dimitar Dimitrov <dimitar@dinux.eu> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 05457af7293..12b84840cd1 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230202 +20230203 diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 893662c74dc..c802587719a 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,12 @@ +2023-02-02 Detlef Vollmann <dv@vollmann.ch> + + Backported from master: + 2022-03-10 Detlef Vollmann <dv@vollmann.ch> + + PR libstdc++/104866 + * include/bits/this_thread_sleep.h: Fix order of #endif and + closing brace of namespace. + 2023-01-18 Jonathan Wakely <jwakely@redhat.com> Backported from master:
reply other threads:[~2023-02-03 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=20230203002004.E08143858C5F@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).