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-8074] Daily bump. Date: Mon, 11 Apr 2022 00:17:11 +0000 (GMT) [thread overview] Message-ID: <20220411001711.714F7385840C@sourceware.org> (raw) https://gcc.gnu.org/g:a1950f5282d2c82fb180689023e234484ac9a61d commit r12-8074-ga1950f5282d2c82fb180689023e234484ac9a61d Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Mon Apr 11 00:16:26 2022 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 8 ++++++++ gcc/testsuite/ChangeLog | 7 +++++++ 3 files changed, 16 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 91fd06443a0..e1ce52db7e0 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220410 +20220411 diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index 03283282c27..39840327d31 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,11 @@ +2022-04-10 Harald Anlauf <anlauf@gmx.de> + + PR fortran/105184 + * array.cc (match_subscript): Reject assumed size coarray + specification with missing lower bound. + * resolve.cc (resolve_allocate_expr): Fix logic for checking + allocate-coshape-spec in ALLOCATE statement. + 2022-04-05 Sandra Loosemore <sandra@codesourcery.com> * trans-openmp.cc (gfc_split_omp_clauses): Fix mask for diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index ef6827bfa00..52aa5495647 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,10 @@ +2022-04-10 Harald Anlauf <anlauf@gmx.de> + + PR fortran/105184 + * gfortran.dg/coarray_44.f90: Adjust expected output. + * gfortran.dg/coarray_allocate_11.f90: Likewise. + * gfortran.dg/coarray_allocate_12.f90: New test. + 2022-04-09 David Malcolm <dmalcolm@redhat.com> PR analyzer/103892
reply other threads:[~2022-04-11 0:17 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=20220411001711.714F7385840C@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).