From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: "jvdelisle@charter.net" <jvdelisle@charter.net>
Cc: fortran@gcc.gnu.org, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] PR 70235 - [4.9/5/6 Regression] Incorrect output with PF format
Date: Wed, 30 Mar 2016 21:40:00 -0000 [thread overview]
Message-ID: <37AA9A18-62FB-4A26-A7CF-3039DC3FB83B@lps.ens.fr> (raw)
In-Reply-To: <56FC3962.1080002@charter.net>
Thanks for the quick review. Committed on trunk as revision r234600. I’ll wait a week for gcc-5 and gcc-4.9.
Dominique
> Le 30 mars 2016 à 22:38, Jerry DeLisle <jvdelisle@charter.net> a écrit :
>
> On 03/30/2016 01:18 PM, Dominique d'Humières wrote:
>> Is the following patch OK for trunk and the gcc-4.9 and gcc-5 branches after some delay (bootstrapped and regtested on x86_64-apple-darwin15)?
>
> Yes, OK, thanks for help!!
>
> Jerry
prev parent reply other threads:[~2016-03-30 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 20:19 Dominique d'Humières
2016-03-30 20:39 ` Jerry DeLisle
2016-03-30 21:40 ` Dominique d'Humières [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=37AA9A18-62FB-4A26-A7CF-3039DC3FB83B@lps.ens.fr \
--to=dominiq@lps.ens.fr \
--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).