From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR fortran/51434 -- ICE in gfc_simplify_transfer
Date: Thu, 01 Mar 2018 21:01:00 -0000 [thread overview]
Message-ID: <20180301210010.GA44709@troutmask.apl.washington.edu> (raw)
In-Reply-To: <95b036ef-b66e-ac22-4eac-8eb6271bf33b@netcologne.de>
On Thu, Mar 01, 2018 at 09:44:57PM +0100, Thomas Koenig wrote:
> Hi Steve,
>
> > 2018-02-26 Steven G. Kargl <kargl@gcc.gnu.org>
> >
> > PF fortran/51434
> > * simplify.c (gfc_simplify_transfer): Reduce mold.
>
> I think this should be "Resolve" (at least that is what your
> patch shows).
>
> OK for trunk, thanks for the patch!
>
Yes, I noticed that typo. I tried gfc_reduce_expr and
gfc_simplify_expr, but both gave the ICE. gfc_resolve_expr
works.
--
Steve
prev parent reply other threads:[~2018-03-01 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 20:15 Steve Kargl
2018-03-01 20:45 ` Thomas Koenig
2018-03-01 21:01 ` Steve Kargl [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=20180301210010.GA44709@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).