public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: Thomas Koenig <tkoenig@netcologne.de>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Set implicit ASYNCHRONOUS attribute
Date: Sat, 07 Oct 2017 02:47:00 -0000	[thread overview]
Message-ID: <ec2b2127-07f0-15ad-f2d4-9e4947774520@charter.net> (raw)
In-Reply-To: <79bae0fe-3a6b-71ff-46de-4bb08ec2de5c@netcologne.de>

On 10/04/2017 02:41 PM, Thomas Koenig wrote:
> Hello world,
> 
> the attached patch sets the implicit ASYNCHRONPUS according to F2008,
> 9.6.2.5:
> 
> # If a variable is used in an asynchronous data transfer statement as
> # • an item in an input/output list,
> # • a group object in a namelist, or
> # • a SIZE= specifier
> # the base object of the data-ref is implicitly given the ASYNCHRONOUS attribute
> in the scoping unit of the
> # data transfer statement. This attribute may be confirmed by explicit declaration.
> 
> At the moment, the only thing this does is show up on the fortran tree
> dump. This will hopefully change once asynchronous I/O is implemented.
> And if you are wondering why I put setting the global variable into
> check_io_constraints: It is because the parsing of the YES/NO
> is done there, and I didn't want to duplicate the code.
> 
> No test case because we don't (yet) have tests for -fdump-fortran-original.
> 
> Regression-tested.  OK for trunk?

OK and thanks for the patch.

Jerry

      reply	other threads:[~2017-10-07  2:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 21:41 Thomas Koenig
2017-10-07  2:47 ` 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=ec2b2127-07f0-15ad-f2d4-9e4947774520@charter.net \
    --to=jvdelisle@charter.net \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).