public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Janus Weil <janus@gcc.gnu.org>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
		gcc-patches <gcc-patches@gcc.gnu.org>,
	Damian Rouson <damian@sourceryinstitute.org>,
		David Kinniburgh <davidgkinniburgh@yahoo.co.uk>
Subject: Re: [Patch, fortran] PR82173 (PDT) - [meta-bug] Parameterized derived type errors
Date: Tue, 12 Sep 2017 18:16:00 -0000	[thread overview]
Message-ID: <CAGkQGi+k7+WqkuUZESR-8ym_M=3k1CSvxuGwOOsEz_3a3DP4pA@mail.gmail.com> (raw)
In-Reply-To: <CAKwh3qh6MBnLaB=7EmX7jv8S2v-UjbkR=8b+4dp5LFbgbYhr6Q@mail.gmail.com>

Hi Janus et al.,

I had to do this quickly because of time pressure and I thought it to
be most efficient while the main patch was fresh in my mind.

Committed as revision 252039 with attributions suitably modified.

Thanks

Paul


On 11 September 2017 at 20:50, Janus Weil <janus@gcc.gnu.org> wrote:
> Hi Paul,
>
>> I have fixed all the PDT bugs that have been reported to me so far in
>> the attached patch. The patch is straightforward and is commented for
>> clarity where necessary. Please note that whitespace changes have been
>> suppressed. For this reason, if you are tempted to try the patch use
>> the -l option when you apply it.
>>
>> Bootstrapped and regtested on FC23/x86_64 - OK for trunk?
>
> yes, looks good to me (except that you seem to confuse me with Thomas
> - I recognize those test cases as mine ;)
>
> Thanks for taking care of this so quickly!
>
> Cheers,
> Janus



-- 
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein

  parent reply	other threads:[~2017-09-12 18:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 19:16 Paul Richard Thomas
2017-09-11 19:50 ` Janus Weil
2017-09-12  7:08   ` Paul Richard Thomas
2017-09-12 18:16   ` Paul Richard Thomas [this message]
2017-09-12 12:47 Dominique d'Humières
2017-09-12 17:28 ` Paul Richard Thomas

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='CAGkQGi+k7+WqkuUZESR-8ym_M=3k1CSvxuGwOOsEz_3a3DP4pA@mail.gmail.com' \
    --to=paul.richard.thomas@gmail.com \
    --cc=damian@sourceryinstitute.org \
    --cc=davidgkinniburgh@yahoo.co.uk \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=janus@gcc.gnu.org \
    --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).