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 r10-9355] Daily bump. Date: Wed, 10 Feb 2021 00:17:52 +0000 (GMT) [thread overview] Message-ID: <20210210001752.4D78E385800D@sourceware.org> (raw) https://gcc.gnu.org/g:617caf75f69ff84435ab4f9ffe7f87f4ba8b747e commit r10-9355-g617caf75f69ff84435ab4f9ffe7f87f4ba8b747e Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Wed Feb 10 00:17:23 2021 +0000 Daily bump. Diff: --- gcc/ChangeLog | 8 ++++++++ gcc/DATESTAMP | 2 +- libstdc++-v3/ChangeLog | 9 +++++++++ 3 files changed, 18 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 36874dab450..ae922d69f7d 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,11 @@ +2021-02-09 Eric Botcazou <ebotcazou@adacore.com> + + PR rtl-optimization/96015 + * reorg.c (skip_consecutive_labels): Minor comment tweaks. + (relax_delay_slots): When deleting a jump to the next active + instruction over a barrier, first delete the barrier if the + jump is the only way to reach the target label. + 2021-02-04 Vladimir N. Makarov <vmakarov@redhat.com> PR target/97701 diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 69950ec5a7c..0f49558f494 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20210209 +20210210 diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 2ab87abd003..38c87c7b42d 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,12 @@ +2021-02-09 Jonathan Wakely <jwakely@redhat.com> + + Backported from master: + 2021-02-09 Jonathan Wakely <jwakely@redhat.com> + + PR libstdc++/99021 + * include/std/coroutine (coroutine_handle<P>::from_address): Add + noexcept. + 2021-01-13 Jonathan Wakely <jwakely@redhat.com> PR libstdc++/98605
reply other threads:[~2021-02-10 0:17 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=20210210001752.4D78E385800D@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).