public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at verizon dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38122] "file already opened in another unit" error when opening /dev/null or /dev/tty twice
Date: Sat, 15 Nov 2008 19:15:00 -0000 [thread overview]
Message-ID: <20081115191352.29249.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38122-14861@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from jvdelisle at verizon dot net 2008-11-15 19:13 -------
Subject: Re: "file already opened in another unit" error
when opening /dev/null or /dev/tty twice
> Which OP? The originator of the c.l.f thread or the originator of
> this bug report.
Originator of this bug report. And what I am trying to say is that the NONMEM
folks could write their code so that it does not violate the standard and deals
with any need for multi-threading.
>
> As Tobias points out, attaching 2 or more unit numbers to the same
> file would open gfortran to race conditions.
Agree, don't attach 2 or more unit numbers to the same file. I have written
rudimentary multi-tasking and multi-threading code myself even when not
supported by the OS. Yes, its extra work and most system programmers would
cringe at the thought of doing that in Fortran. Respectfully, the NONMEM team
needs to fix their code.
> $0.02
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38122
next prev parent reply other threads:[~2008-11-15 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 18:15 [Bug fortran/38122] New: " steven dot chapel at sbcglobal dot net
2008-11-14 18:41 ` [Bug fortran/38122] " kargl at gcc dot gnu dot org
2008-11-14 20:20 ` steve dot chapel at a2pg dot com
2008-11-14 20:56 ` kargl at gcc dot gnu dot org
2008-11-15 10:43 ` burnus at gcc dot gnu dot org
2008-11-15 15:00 ` jvdelisle at gcc dot gnu dot org
2008-11-15 17:30 ` kargl at gcc dot gnu dot org
2008-11-15 19:15 ` jvdelisle at verizon dot net [this message]
2008-11-15 20:53 ` jvdelisle at gcc dot gnu dot org
2009-01-05 20:23 ` mikael at gcc dot gnu dot org
2009-01-18 1:33 ` jvdelisle at gcc dot gnu dot 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=20081115191352.29249.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: 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).