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-11128] Daily bump. Date: Mon, 19 Dec 2022 00:19:44 +0000 (GMT) [thread overview] Message-ID: <20221219001944.7739D396A672@sourceware.org> (raw) https://gcc.gnu.org/g:1b00f6e75a8411cb4eacd0387648d297717c6c2e commit r10-11128-g1b00f6e75a8411cb4eacd0387648d297717c6c2e Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Mon Dec 19 00:19:04 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 8b45390a1dd..11fabd49cf9 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221218 +20221219 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 545420f2fba..afc41fbe6a8 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,12 @@ +2022-12-18 Paul Thomas <pault@gcc.gnu.org> + + Backported from master: + 2022-12-09 Paul Thomas <pault@gcc.gnu.org> + + PR fortran/107872 + * resolve.c (derived_inaccessible): Skip over allocatable components + to prevent an infinite loop. + 2022-11-25 Harald Anlauf <anlauf@gmx.de> Backported from master: diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 3c034c8bf89..e3701cfde8e 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2022-12-18 Paul Thomas <pault@gcc.gnu.org> + + Backported from master: + 2022-12-09 Paul Thomas <pault@gcc.gnu.org> + + PR fortran/107872 + * gfortran.dg/pr107872.f90: New test. + 2022-12-16 Patrick Palka <ppalka@redhat.com> Backported from master:
reply other threads:[~2022-12-19 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=20221219001944.7739D396A672@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).