From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"Jürgen Reuter" <juergen.reuter@desy.de>
Subject: Re: [Patch, fortran] PR87336] [8/9 regression] wrong output for pointer dummy assiocated to target actual argument
Date: Tue, 18 Sep 2018 17:51:00 -0000 [thread overview]
Message-ID: <CAGkQGiLYVK55R6RBjxg+K1-xRvZMy9txf98P=L5_zp7z3v9iBg@mail.gmail.com> (raw)
In-Reply-To: <dc992985-7f29-4b44-689c-87c574b0ce24@netcologne.de>
Thanks Thomas,
I'll take a look at your in a few minutes.
Cheers
Paul
On 18 September 2018 at 18:50, Thomas Koenig <tkoenig@netcologne.de> wrote:
> Hi Paul,
>
>> Bootstraps and regtests on FC28/x86_64 - OK for 8- and 9-branches?
>
>
> OK. Thanks for the patch!
>
> Regards
>
> Thomas
--
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein
prev parent reply other threads:[~2018-09-18 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 9:37 Paul Richard Thomas
2018-09-18 17:50 ` Thomas Koenig
2018-09-18 17:51 ` Paul Richard Thomas [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='CAGkQGiLYVK55R6RBjxg+K1-xRvZMy9txf98P=L5_zp7z3v9iBg@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=juergen.reuter@desy.de \
--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).