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-11056] Daily bump. Date: Mon, 24 Oct 2022 00:19:06 +0000 (GMT) [thread overview] Message-ID: <20221024001906.70E0C3856DC3@sourceware.org> (raw) https://gcc.gnu.org/g:968bc227856e3a71c1fdc132a91c1c94c18f171c commit r10-11056-g968bc227856e3a71c1fdc132a91c1c94c18f171c Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Mon Oct 24 00:18:27 2022 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 10 ++++++++++ gcc/testsuite/ChangeLog | 9 +++++++++ 3 files changed, 20 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index e09d253a0d6..9c3fc6cabad 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221023 +20221024 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 491c0c2cbd5..032b92fa687 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,13 @@ +2022-10-23 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2022-10-20 Harald Anlauf <anlauf@gmx.de> + Steven G. Kargl <kargl@gcc.gnu.org> + + PR fortran/105633 + * expr.c (find_array_section): Move check for NULL pointers so + that both subscript triplets and vector subscripts are covered. + 2022-10-10 Mikael Morin <mikael@gcc.gnu.org> Backported from master: diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 4294c75417a..db5e5ee60f6 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,12 @@ +2022-10-23 Harald Anlauf <anlauf@gmx.de> + + Backported from master: + 2022-10-20 Harald Anlauf <anlauf@gmx.de> + Steven G. Kargl <kargl@gcc.gnu.org> + + PR fortran/105633 + * gfortran.dg/pr105633.f90: New test. + 2022-10-21 Richard Sandiford <richard.sandiford@arm.com> Backported from master:
reply other threads:[~2022-10-24 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=20221024001906.70E0C3856DC3@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: linkBe 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).