public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janus Weil <janus@gcc.gnu.org>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: gfortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran, F03] PR 64508: interface check missing for procedure pointer component as actual argument
Date: Sun, 11 Jan 2015 17:39:00 -0000	[thread overview]
Message-ID: <CAKwh3qi9T2+mQViezphdxTR2GymwaGJjd-Y8g4ipMDAk1Rzevg@mail.gmail.com> (raw)
In-Reply-To: <CAGkQGiKKZ6SXsubRVYO53SkWcsWA4Zp1a+t0b+rA+aEVR4-1Kw@mail.gmail.com>

Committed as r219431. Thanks for the review!

Cheers,
Janus



2015-01-11 16:16 GMT+01:00 Paul Richard Thomas <paul.richard.thomas@gmail.com>:
> Dear Janus,
>
> As you say, the patch is pretty straightforward :-) OK for trunk.
>
> Thanks for the patch
>
> Paul
>
> On 11 January 2015 at 11:21, Janus Weil <janus@gcc.gnu.org> wrote:
>> Ping! (I think this patch is pretty straightforward ...)
>>
>> Cheers,
>> Janus
>>
>>
>>
>> 2015-01-06 16:19 GMT+01:00 Janus Weil <janus@gcc.gnu.org>:
>>> Hi all,
>>>
>>> here is a patch which adds an interface check for procedure pointer
>>> components as acual arguments. Such a check is there already for
>>> ordinary procedures and procedure pointers, but missing for PPCs. It
>>> checks the interface of the actual argument versus the interface of
>>> the dummy procedure, according to the usual rules.
>>>
>>> Regtested on x86_64-unknown-linux-gnu. Ok for trunk?
>>>
>>> Cheers,
>>> Janus
>>>
>>>
>>>
>>> 2015-01-06  Janus Weil  <janus@gcc.gnu.org>
>>>
>>>     PR fortran/64508
>>>     * interface.c (compare_parameter): Interface check for
>>>     procedure-pointer component as actual argument.
>>>
>>> 2015-01-06  Janus Weil  <janus@gcc.gnu.org>
>>>
>>>     PR fortran/64508
>>>     * gfortran.dg/proc_ptr_comp_41.f90: New.
>
>
>
> --
> Outside of a dog, a book is a man's best friend. Inside of a dog it's
> too dark to read.
>
> Groucho Marx

      reply	other threads:[~2015-01-11 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 15:19 Janus Weil
2015-01-11 11:40 ` Janus Weil
2015-01-11 15:53   ` Paul Richard Thomas
2015-01-11 17:39     ` Janus Weil [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=CAKwh3qi9T2+mQViezphdxTR2GymwaGJjd-Y8g4ipMDAk1Rzevg@mail.gmail.com \
    --to=janus@gcc.gnu.org \
    --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).