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 r10-11048] Daily bump.
Date: Fri, 21 Oct 2022 00:19:54 +0000 (GMT) [thread overview]
Message-ID: <20221021001954.9977F3858D38@sourceware.org> (raw)
https://gcc.gnu.org/g:da6b16d3ec808828e54218f26a9654c3b0c63228
commit r10-11048-gda6b16d3ec808828e54218f26a9654c3b0c63228
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Fri Oct 21 00:19:16 2022 +0000
Daily bump.
Diff:
---
gcc/ChangeLog | 10 ++++++++++
gcc/DATESTAMP | 2 +-
gcc/testsuite/ChangeLog | 8 ++++++++
3 files changed, 19 insertions(+), 1 deletion(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 41998460e75..43c15288d7c 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,13 @@
+2022-10-20 Kewen Lin <linkw@linux.ibm.com>
+
+ Backported from master:
+ 2022-09-26 Kewen Lin <linkw@linux.ibm.com>
+
+ PR target/96072
+ * config/rs6000/rs6000-logue.c (rs6000_emit_epilogue): Update the
+ condition for adding REG_CFA_DEF_CFA reg note with
+ frame_pointer_needed_indeed.
+
2022-10-17 Pat Haugen <pthaugen@linux.ibm.com>
PR target/99685
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 8b08eddd863..0f7d77c700e 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20221020
+20221021
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index fe2da634ac5..a1062409152 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2022-10-20 Kewen Lin <linkw@linux.ibm.com>
+
+ Backported from master:
+ 2022-09-26 Kewen Lin <linkw@linux.ibm.com>
+
+ PR target/96072
+ * gcc.target/powerpc/pr96072.c: New test.
+
2022-10-14 Richard Biener <rguenther@suse.de>
Backported from master:
reply other threads:[~2022-10-21 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=20221021001954.9977F3858D38@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).