From: Jerry DeLisle <jvdelisle@charter.net>
To: "Nicolas Koenig" <koenigni@student.ethz.ch>,
"Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
gfortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR35339 Optimize implied do loops in io statements
Date: Sat, 03 Jun 2017 16:25:00 -0000 [thread overview]
Message-ID: <5e1bd32c-de24-8f95-ecf2-0ab76abb6092@charter.net> (raw)
In-Reply-To: <ce3115b3-0123-2fc6-a390-ee3318e35e60@student.ethz.ch>
On 06/03/2017 06:48 AM, Nicolas Koenig wrote:
> Hello everyone,
>
> here is a version of the patch that includes a workaround for PR 80960. I have
> also included a separate test case for the failure that Dominique detected. The
> style issues should be fixed.
>
> Regression-tested. OK for trunk?
>
Yes, OK.
Thanks for the work.
Jerry
next prev parent reply other threads:[~2017-06-03 16:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 15:49 Dominique d'Humières
2017-05-29 16:24 ` Nicolas Koenig
2017-05-29 16:51 ` Dominique d'Humières
2017-05-31 15:40 ` Bernhard Reutner-Fischer
2017-05-31 15:49 ` Dominique d'Humières
2017-05-31 19:03 ` Dominique d'Humières
2017-05-31 23:15 ` Nicolas Koenig
2017-06-01 9:31 ` Dominique d'Humières
2017-06-01 14:19 ` Dominique d'Humières
2017-06-01 14:37 ` Dominique d'Humières
2017-06-01 18:26 ` Nicolas Koenig
2017-06-03 13:48 ` Nicolas Koenig
2017-06-03 16:25 ` Jerry DeLisle [this message]
2017-06-03 18:12 ` Bernhard Reutner-Fischer
2017-06-05 20:39 ` Nicolas Koenig
2017-06-06 11:05 ` Markus Trippelsdorf
2017-06-07 15:13 ` Renlin Li
2017-11-02 8:25 ` [testsuite, committed] Fix scan pattern in gfortran.dg/implied_do_io_1.f90 Tom de Vries
-- strict thread matches above, loose matches on Subject: below --
2017-05-27 19:49 [Patch, fortran] PR35339 Optimize implied do loops in io statements Nicolas Koenig
2017-05-28 22:07 ` Jerry DeLisle
2017-05-28 23:32 ` Nicolas Koenig
2017-05-29 6:40 ` Thomas Koenig
2017-05-29 14:06 ` Thomas Koenig
2017-05-29 15:32 ` Jerry DeLisle
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=5e1bd32c-de24-8f95-ecf2-0ab76abb6092@charter.net \
--to=jvdelisle@charter.net \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=koenigni@student.ethz.ch \
--cc=rep.dot.nop@gmail.com \
/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).