From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Jerry DeLisle <jvdelisle@charter.net>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR99818 - [10/11 Regression] ICE in gfc_get_tree_for_caf_expr, at fortran/trans-expr.c:2186
Date: Mon, 5 Apr 2021 07:24:25 +0100 [thread overview]
Message-ID: <CAGkQGiJdR4nfYCPcRwTHzV9ztiXVvhs9xwbadVTYX5m8uowP5Q@mail.gmail.com> (raw)
In-Reply-To: <0fb52949-d275-6dd8-8dc9-84f68ea7ba3c@charter.net>
Hi Jerry,
A belated thanks is in order. Pushed as
fc27115d6107f219e6f3dc610c99210005fe9dc5. I'll wait a little while for
10-branch since it is an ICE on wrong code.
Regards
Paul
On Fri, 2 Apr 2021 at 04:11, Jerry DeLisle <jvdelisle@charter.net> wrote:
> Paul,
>
> This looks OK to me for Trunk. I believe 10 is in freeze so it may have
> to wait or get release manager approval.
>
> Jerry
>
> On 4/1/21 6:44 AM, Paul Richard Thomas via Fortran wrote:
> > This one is trivial. The wrong error message was transformed by my patch
> > for PR98897 into an ICE. This patch now produces the correct error.
> >
> > Regtests OK on FC33/x86_64 - OK for the affected branches?
> >
> > Paul
> >
> > Fortran: Fix ICE on wrong code [PR99818].
> >
> > 2021-04-01 Paul Thomas <pault@gcc.gnu.org>
> >
> > gcc/fortran/ChangeLog
> >
> > PR fortran/99818
> > * interface.c (compare_parameter): The codimension attribute is
> > applied to the _data field of class formal arguments.
> >
> > gcc/testsuite/ChangeLog
> >
> > PR fortran/99818
> > * gfortran.dg/coarray_48.f90: New test.
>
>
--
"If you can't explain it simply, you don't understand it well enough" -
Albert Einstein
prev parent reply other threads:[~2021-04-05 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 13:44 Paul Richard Thomas
2021-04-02 3:11 ` Jerry DeLisle
2021-04-05 6:24 ` Paul Richard Thomas [this message]
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=CAGkQGiJdR4nfYCPcRwTHzV9ztiXVvhs9xwbadVTYX5m8uowP5Q@mail.gmail.com \
--to=paul.richard.thomas@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@charter.net \
/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).