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-8741] Daily bump.
Date: Sun, 4 Sep 2022 00:21:27 +0000 (GMT) [thread overview]
Message-ID: <20220904002127.082B93858C20@sourceware.org> (raw)
https://gcc.gnu.org/g:29b456e0676e051720e030ab801be0479554658a
commit r12-8741-g29b456e0676e051720e030ab801be0479554658a
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Sun Sep 4 00:20:49 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 564a4c3847c..04366bbe256 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,12 @@
+2022-09-03 Peter Bergner <bergner@linux.ibm.com>
+
+ Backported from master:
+ 2022-09-01 Peter Bergner <bergner@linux.ibm.com>
+
+ PR target/101322
+ * config/rs6000/rs6000-builtin.cc (rs6000_gimple_fold_mma_builtin):
+ Enforce the use of a valid MMA pointer type.
+
2022-09-02 Richard Earnshaw <rearnsha@arm.com>
Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index e15744dd99e..999da9a9e8d 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220903
+20220904
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 356a9a19402..da17094268e 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2022-09-03 Peter Bergner <bergner@linux.ibm.com>
+
+ Backported from master:
+ 2022-09-01 Peter Bergner <bergner@linux.ibm.com>
+
+ PR target/101322
+ * g++.target/powerpc/pr101322.C: New test.
+
2022-08-30 Tobias Burnus <tobias@codesourcery.com>
Backported from master:
reply other threads:[~2022-09-04 0:21 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=20220904002127.082B93858C20@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).