From: Jerry DeLisle <jvdelisle@charter.net>
To: sgk@troutmask.apl.washington.edu, fortran@gcc.gnu.org,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR fortran/83939 -- Enforce F2018 C15100
Date: Mon, 12 Mar 2018 02:04:00 -0000 [thread overview]
Message-ID: <9c916a52-aa08-a587-eab9-0a5686fc57c6@charter.net> (raw)
In-Reply-To: <20180311204849.GB56613@troutmask.apl.washington.edu>
On 03/11/2018 01:48 PM, Steve Kargl wrote:
> The attach patch enforces F2018:C15100. Similar constraints are
> present in older versions of the standard. The patch and testcase
> are sufficiently explanatory. Regression tested on x86_64-*-freebsd.
> OK to commit?
>
Looks OK Steve.
Jerry
>
> 2018-03-11 Steven G. Kargl <kargl@gcc.gnu.org>
>
> PR fortran/83939
> * resolve.c (resolve_fl_procedure): Enforce F2018:C15100.
> 2018-03-11 Steven G. Kargl <kargl@gcc.gnu.org>
>
> PR fortran/83939
> * gfortran.dg/pr83939.f90
>
prev parent reply other threads:[~2018-03-12 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 20:48 Steve Kargl
2018-03-12 2:04 ` Jerry DeLisle [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=9c916a52-aa08-a587-eab9-0a5686fc57c6@charter.net \
--to=jvdelisle@charter.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).