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-10269] Daily bump.
Date: Fri, 23 Sep 2022 00:21:14 +0000 (GMT) [thread overview]
Message-ID: <20220923002114.354923858D38@sourceware.org> (raw)
https://gcc.gnu.org/g:f2274fadac4c2a5696f03d0c3b578ff2686bd4da
commit r11-10269-gf2274fadac4c2a5696f03d0c3b578ff2686bd4da
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Fri Sep 23 00:20:37 2022 +0000
Daily bump.
Diff:
---
gcc/DATESTAMP | 2 +-
gcc/fortran/ChangeLog | 9 +++++++++
gcc/testsuite/ChangeLog | 8 ++++++++
3 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 6fbb09fe858..44f77519800 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220922
+20220923
diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog
index 79c9816384e..81c5f380d1e 100644
--- a/gcc/fortran/ChangeLog
+++ b/gcc/fortran/ChangeLog
@@ -1,3 +1,12 @@
+2022-09-22 Harald Anlauf <anlauf@gmx.de>
+
+ Backported from master:
+ 2022-09-15 Harald Anlauf <anlauf@gmx.de>
+
+ PR fortran/106857
+ * simplify.c (gfc_simplify_pack): Check for NULL pointer dereferences
+ while walking through constructors (error recovery).
+
2022-09-05 José Rui Faustino de Sousa <jrfsousa@gmail.com>
Backported from master:
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 961a2246213..ea0057df87d 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2022-09-22 Harald Anlauf <anlauf@gmx.de>
+
+ Backported from master:
+ 2022-09-15 Harald Anlauf <anlauf@gmx.de>
+
+ PR fortran/106857
+ * gfortran.dg/pr106857.f90: New test.
+
2022-09-13 Kewen Lin <linkw@linux.ibm.com>
Backported from master:
reply other threads:[~2022-09-23 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=20220923002114.354923858D38@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).