From: Renlin Li <renlin.li@foss.arm.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>,
Nicolas Koenig <koenigni@student.ethz.ch>
Cc: "Jerry DeLisle" <jvdelisle@charter.net>,
"Dominique d'Humières" <dominiq@lps.ens.fr>,
"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: Wed, 07 Jun 2017 15:13:00 -0000 [thread overview]
Message-ID: <593817FD.6090506@foss.arm.com> (raw)
In-Reply-To: <20170606110520.GA286@x4>
171.swim fails on aarch64-linux as well. I dis a bisect and confirm it's r248877 causing
the miscompare.
Regards,
Renlin
On 06/06/17 12:05, Markus Trippelsdorf wrote:
> On 2017.06.05 at 22:39 +0200, Nicolas Koenig wrote:
>> With all the style fixes committed as r248877.
>
> 171_swim fails now. I didn't bisect, but I suspect your revision.
>
next prev parent reply other threads:[~2017-06-07 15:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 15:49 Dominique d'Humières
2017-05-29 16:08 ` Nicolas Koenig
2017-05-29 16:34 ` Dominique d'Humières
2017-05-31 6:49 ` Bernhard Reutner-Fischer
2017-05-31 15:49 ` Dominique d'Humières
2017-05-31 16:04 ` Dominique d'Humières
2017-05-31 19:11 ` Nicolas Koenig
2017-05-31 23:34 ` Bernhard Reutner-Fischer
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-03 13:48 ` Nicolas Koenig
2017-06-03 16:25 ` Jerry DeLisle
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 [this message]
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 21:47 [Patch, fortran] PR35339 Optimize implied do loops in io statements Nicolas Koenig
2017-05-28 22:09 ` 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=593817FD.6090506@foss.arm.com \
--to=renlin.li@foss.arm.com \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@charter.net \
--cc=koenigni@student.ethz.ch \
--cc=markus@trippelsdorf.de \
--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).