public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/25829] [F2003] Asynchronous IO support Date: Fri, 08 Jan 2010 10:11:00 -0000 [thread overview] Message-ID: <20100108101119.13786.qmail@sourceware.org> (raw) In-Reply-To: <bug-25829-11659@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from burnus at gcc dot gnu dot org 2010-01-08 10:11 ------- For completeness: I just committed support for the ASYNCHRONOUS attribute: http://gcc.gnu.org/ml/fortran/2010-01/msg00049.html http://gcc.gnu.org/ml/gcc-cvs/2010-01/msg00192.html which is treated as no op. One needs to think carefully whether one needs to take care of ASYNCHRONOUS for the middle end when real async I/O is implemented. For a simple: write(9, ..., asynchronous='yes') foo ... write(9, ...) ! force WAIT on unit 9 foo = 8 presumably not using "&foo" in the first write call lets the address escape thus unless a function is known (to the ME) to not touch "foo" (indirectly), no problem should occur. But how about: ! Note: using "foo" in AIO implies the ASYNCHRONOUS attribute for foo write(9, ..., asynchronous='yes', id=waitid) foo call finish(foo, waitid) contains subroutine finish(var, wait) asynchronous :: var wait(wait) var = 7 end subroutine finish Here, the ME might be tempted to change the order of WAIT and "var = 7"; thus in this case we probably need to tell the ME about the ASYNCHRONOUS attribute. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829
next prev parent reply other threads:[~2010-01-08 10:11 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-17 21:53 [Bug fortran/25829] New: " jb at gcc dot gnu dot org 2006-01-17 23:33 ` [Bug fortran/25829] " pinskia at gcc dot gnu dot org 2008-02-17 1:20 ` jvdelisle at gcc dot gnu dot org 2008-02-17 5:02 ` jvdelisle at gcc dot gnu dot org 2008-02-23 16:49 ` jvdelisle at gcc dot gnu dot org 2008-04-05 22:19 ` jvdelisle at gcc dot gnu dot org 2008-04-05 22:24 ` jvdelisle at gcc dot gnu dot org 2008-04-05 22:35 ` jvdelisle at gcc dot gnu dot org 2008-04-07 22:07 ` jvdelisle at gcc dot gnu dot org 2008-04-07 22:09 ` jvdelisle at gcc dot gnu dot org 2008-04-07 22:12 ` jvdelisle at gcc dot gnu dot org 2009-04-10 21:23 ` dfranke at gcc dot gnu dot org 2009-04-11 15:26 ` jvdelisle at gcc dot gnu dot org 2009-10-28 22:03 ` jb at gcc dot gnu dot org 2009-12-11 22:28 ` burnus at gcc dot gnu dot org 2009-12-11 22:29 ` burnus at gcc dot gnu dot org 2010-01-08 10:11 ` burnus at gcc dot gnu dot org [this message] 2010-01-08 10:42 ` burnus at gcc dot gnu dot org 2010-07-13 17:34 ` burnus at gcc dot gnu dot org [not found] <bug-25829-4@http.gcc.gnu.org/bugzilla/> 2011-03-04 18:08 ` burnus at gcc dot gnu.org 2011-03-04 18:12 ` jakub at gcc dot gnu.org 2011-04-15 9:11 ` burnus at gcc dot gnu.org 2011-07-13 9:25 ` burnus at gcc dot gnu.org 2011-07-13 13:16 ` burnus at gcc dot gnu.org
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=20100108101119.13786.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).