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
Subject: [gcc r12-8369] Daily bump.
Date: Thu, 12 May 2022 00:19:41 +0000 (GMT)	[thread overview]
Message-ID: <20220512001941.8E69C3857432@sourceware.org> (raw)

https://gcc.gnu.org/g:f363017e8bc7d9a4619a4b1233737bbcebbc0c08

commit r12-8369-gf363017e8bc7d9a4619a4b1233737bbcebbc0c08
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Thu May 12 00:19:06 2022 +0000

    Daily bump.

Diff:
---
 gcc/ChangeLog           | 9 +++++++++
 gcc/DATESTAMP           | 2 +-
 gcc/testsuite/ChangeLog | 8 ++++++++
 3 files changed, 18 insertions(+), 1 deletion(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index d48c36f5d09..effb583864f 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,12 @@
+2022-05-11  Martin Jambor  <mjambor@suse.cz>
+
+	Backported from master:
+	2022-04-29  Martin Jambor  <mjambor@suse.cz>
+
+	PR ipa/100413
+	* cgraph.cc (cgraph_node::remove): Release body of the node this
+	is clone_of if appropriate.
+
 2022-05-10  Jakub Jelinek  <jakub@redhat.com>
 
 	Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 3e06743d939..2a18b643483 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220511
+20220512
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index f9d25cb8173..3d076df5697 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2022-05-11  Martin Jambor  <mjambor@suse.cz>
+
+	Backported from master:
+	2022-04-29  Martin Jambor  <mjambor@suse.cz>
+
+	PR ipa/100413
+	* g++.dg/ipa/pr100413.C: New test.
+
 2022-05-10  H.J. Lu  <hjl.tools@gmail.com>
 
 	Backported from master:


                 reply	other threads:[~2022-05-12  0:19 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=20220512001941.8E69C3857432@sourceware.org \
    --to=gccadmin@gcc.gnu.org \
    --cc=gcc-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).