public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	       gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR 49636 - [F03] ASSOCIATE construct confused with slightly complicated case
Date: Sat, 19 May 2018 15:53:00 -0000	[thread overview]
Message-ID: <20180519155342.GB95604@troutmask.apl.washington.edu> (raw)
In-Reply-To: <CAGkQGiJnjuMbFyB52ASeiVGa0u=5jp1JoY8VN0BLuKW7Lk3c4g@mail.gmail.com>

On Sat, May 19, 2018 at 04:42:35PM +0100, Paul Richard Thomas wrote:
> This patch is a straightforward recycling of existing code to replace
> an incomplete copy elsewhere.
> 
> Bootstraps and regtests on FC27/x86_64 - OK for trunk down to 7-branch?
> 

OK.

-- 
Steve

      reply	other threads:[~2018-05-19 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-19 15:42 Paul Richard Thomas
2018-05-19 15:53 ` 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=20180519155342.GB95604@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=paul.richard.thomas@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).