public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/30617] recursive I/O hangs under OSX Date: Thu, 08 Feb 2007 16:18:00 -0000 [thread overview] Message-ID: <20070208161813.25128.qmail@sourceware.org> (raw) In-Reply-To: <bug-30617-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #20 from kargl at gcc dot gnu dot org 2007-02-08 16:18 ------- (In reply to comment #17) > > Now, if Fortran2003 allows some recursive access to the same unit > (under which conditions?), Recursive IO to external units is simply not allowed by the Fortran 95 and Fortran 2003 standards. You could wade through Brooks posts in fortran@ to see where recursion is allowed. > __gthread_recursive_mutex_t as well as the initializer, perhaps together with > adding a recursion count (as the recursion count in __gthread_recursive_mutex_t > isn't portably accessible) to gfc_unit as well. The question is how much is > libgfortran prepared for changes happening to gfc_unit happening between > say st_write and st_write_done calls (st_write normally calls get_unit and thus > acquires gfc_unit's lock, which is held until st_write_done calls unlock_unit). > This sound like a performance penalty imposed on anyone writing standard conforming code to permit nonconforming code to run. The fact remains that a fortran processor can do anything it wants with nonconforming code. It might "work" on some architecture and it may "fail" another for some definition of "work" and "fail". So be it. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617
next prev parent reply other threads:[~2007-02-08 16:18 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-27 19:47 [Bug fortran/30617] New: recursive I/O hangs under OSX 10.3 dominiq at lps dot ens dot fr 2007-01-27 21:31 ` [Bug fortran/30617] " kargl at gcc dot gnu dot org 2007-01-27 21:38 ` kargl at gcc dot gnu dot org 2007-01-27 21:43 ` dominiq at lps dot ens dot fr 2007-01-27 21:48 ` [Bug libfortran/30617] " pinskia at gcc dot gnu dot org 2007-01-27 21:51 ` jvdelisle at gcc dot gnu dot org 2007-01-27 22:01 ` dominiq at lps dot ens dot fr 2007-01-27 23:34 ` kargl at gcc dot gnu dot org 2007-01-29 13:46 ` dir at lanl dot gov 2007-01-29 14:13 ` dominiq at lps dot ens dot fr 2007-02-05 22:15 ` fxcoudert at gcc dot gnu dot org 2007-02-06 3:04 ` jvdelisle at gcc dot gnu dot org 2007-02-07 9:10 ` brooks at gcc dot gnu dot org 2007-02-07 9:24 ` dominiq at lps dot ens dot fr 2007-02-07 19:55 ` [Bug libfortran/30617] recursive I/O hangs under OSX dominiq at lps dot ens dot fr 2007-02-08 3:12 ` jvdelisle at gcc dot gnu dot org 2007-02-08 8:46 ` dominiq at lps dot ens dot fr 2007-02-08 9:36 ` jakub at gcc dot gnu dot org 2007-02-08 10:03 ` dominiq at lps dot ens dot fr 2007-02-08 12:07 ` dominiq at lps dot ens dot fr 2007-02-08 16:18 ` kargl at gcc dot gnu dot org [this message] 2007-02-11 20:59 ` pault at gcc dot gnu dot org 2007-02-12 7:37 ` dominiq at lps dot ens dot fr 2007-02-17 17:17 ` pault at gcc dot gnu dot org 2007-03-03 13:31 ` fxcoudert at gcc dot gnu dot org 2007-03-03 20:56 ` burnus at gcc dot gnu dot org 2007-03-03 21:46 ` dominiq at lps dot ens dot fr 2007-04-24 10:59 ` jakub at gcc dot gnu dot org 2007-04-24 12:04 ` dominiq at lps dot ens dot fr 2007-04-24 14:46 ` pinskia at gcc dot gnu dot org 2007-04-24 14:59 ` dominiq at lps dot ens dot fr 2008-07-11 22:19 ` dominiq at lps dot ens dot fr 2008-07-11 22:22 ` dominiq at lps dot ens dot fr 2009-05-07 22:00 ` [Bug libfortran/30617] Implement a run time diagnostic for invalid recursive I/O dominiq at lps dot ens dot fr 2009-12-14 20:43 ` dominiq at lps dot ens dot fr 2009-12-14 20:46 ` dominiq at lps dot ens dot fr 2009-12-14 20:52 ` dominiq at lps dot ens dot fr
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=20070208161813.25128.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).