public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Thomas dot Koenig at online dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/18982] open(status="new") does not generate an error if the file exists
Date: Thu, 13 Jan 2005 22:14:00 -0000	[thread overview]
Message-ID: <20050113221411.20558.qmail@sourceware.org> (raw)
In-Reply-To: <20041214133005.18982.Thomas.Koenig@online.de>


------- Additional Comments From Thomas dot Koenig at online dot de  2005-01-13 22:14 -------
(In reply to comment #3)
> Sligtly updated patch:

.. which was broken; http://gcc.gnu.org/ml/gcc-patches/2005-01/msg00024.html
was correct (although it fails due to whitespace changes).

This patch does not fix all that's broken, though.  The following
test cases still fail with my patch:

program open_readonly
  call system("touch tst2.dat ; chmod 100 tst2.dat")
  open(unit=10,file="tst2.dat", err=9000)
  goto 30
9000 continue
  print *,"Opening read-only file failed"
  call abort
30 continue
end program open_readonly

program open_writeonly
  call system("touch tst1.dat ; chmod 200 tst1.dat")
  open(unit=10,file="tst1.dat", err=9000)
  goto 30
9000 continue
  print *,"Opening write-only file failed"
  call abort
30 continue
end program open_writeonly

so something else is needed.

I've removed the "patch" keyword.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|patch                       |


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


  parent reply	other threads:[~2005-01-13 22:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 13:30 [Bug libfortran/18982] New: " Thomas dot Koenig at online dot de
2004-12-14 13:30 ` [Bug libfortran/18982] " Thomas dot Koenig at online dot de
2004-12-14 22:13 ` tobi at gcc dot gnu dot org
2005-01-01 22:07 ` Thomas dot Koenig at online dot de
2005-01-06 14:43 ` tobi at gcc dot gnu dot org
2005-01-12 22:03 ` Thomas dot Koenig at online dot de
2005-01-13 22:14 ` Thomas dot Koenig at online dot de [this message]
2005-01-17 21:00 ` Thomas dot Koenig at online dot de
2005-01-22 19:49 ` cvs-commit at gcc dot gnu dot org
2005-01-22 22:33 ` pbrook 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=20050113221411.20558.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).