public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost dot VandeVondele at pci dot uzh dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/45723]  New: opening /dev/null for appending writes
Date: Sat, 18 Sep 2010 18:34:00 -0000	[thread overview]
Message-ID: <bug-45723-6642@http.gcc.gnu.org/bugzilla/> (raw)

I'm wondering if the following open statement should really fail. I have no
strong opinion, but it would be convenient if it 'just' worked, like you can
open an non-existing file and 'append'.

I guess it is related to the fact that /dev/null can't be seeked.

> cat test.f90
 OPEN(UNIT=7,FILE="/dev/null",FORM="FORMATTED",POSITION="APPEND",IOSTAT=istat)
 IF (istat.NE.0) STOP 1
 END


-- 
           Summary: opening /dev/null for appending writes
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libfortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Joost dot VandeVondele at pci dot uzh dot ch


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45723


             reply	other threads:[~2010-09-18 18:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18 18:34 Joost dot VandeVondele at pci dot uzh dot ch [this message]
2010-09-18 18:35 ` [Bug libfortran/45723] " Joost dot VandeVondele at pci dot uzh dot ch
2010-09-19 20:01 ` jvdelisle at gcc dot gnu dot org
2010-09-20  4:46 ` jvdelisle at gcc dot gnu dot org
2010-09-20  6:30 ` Joost dot VandeVondele at pci dot uzh dot ch
2010-09-22  3:11 ` jvdelisle at gcc dot gnu dot org
2010-09-22 11:31 ` Joost dot VandeVondele at pci dot uzh dot ch
2010-09-22 15:07 ` 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=bug-45723-6642@http.gcc.gnu.org/bugzilla/ \
    --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).