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 r11-10159] Daily bump.
Date: Fri, 22 Jul 2022 00:18:50 +0000 (GMT) [thread overview]
Message-ID: <20220722001850.23CBA3835839@sourceware.org> (raw)
https://gcc.gnu.org/g:bbf4c8820a75ccace739d2739348128a85c67c41
commit r11-10159-gbbf4c8820a75ccace739d2739348128a85c67c41
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Fri Jul 22 00:18:14 2022 +0000
Daily bump.
Diff:
---
gcc/ChangeLog | 8 ++++++++
gcc/DATESTAMP | 2 +-
gcc/testsuite/ChangeLog | 8 ++++++++
3 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 835d5b9c7b9..f61b36f2704 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,11 @@
+2022-07-21 Surya Kumari Jangala <jskumari@linux.vnet.ibm.com>
+
+ Backported from master:
+ 2022-06-14 Surya Kumari Jangala <jskumari@linux.ibm.com>
+
+ PR rtl-optimization/105041
+ * regrename.c (check_new_reg_p): Use nregs value from du chain.
+
2022-07-14 Michael Meissner <meissner@linux.ibm.com>
* config/rs6000/rs6000.c (rs6000_option_override_internal): Do
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index ace4919765e..7bdcd4fa865 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220721
+20220722
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 0f778ba7d02..a51f8edd8ed 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2022-07-21 Surya Kumari Jangala <jskumari@linux.vnet.ibm.com>
+
+ Backported from master:
+ 2022-06-14 Surya Kumari Jangala <jskumari@linux.ibm.com>
+
+ PR rtl-optimization/105041
+ * gcc.target/powerpc/pr105041.c: New test.
+
2022-07-16 Steve Kargl <kargl@gcc.gnu.org>
Backported from master:
reply other threads:[~2022-07-22 0:18 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=20220722001850.23CBA3835839@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).