public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/30162] New: I/O with named pipes does not work Date: Tue, 12 Dec 2006 04:28:00 -0000 [thread overview] Message-ID: <bug-30162-10743@http.gcc.gnu.org/bugzilla/> (raw) Reduced test case frim Bud Davis $ cat a.f integer status integer i open(unit=20,file='np',action='write', & form='unformatted',iostat=status); print*,'status from open is ',status do i = 1,5 write(20)i end do end $ cat b.f integer status integer i integer val open(unit=21,file='np',action='read', & form='unformatted',iostat=status); print*,'status from open is ',status do i = 1,5 read(21)val print*,val end do Here is what I get: $ mkfifo np $ ./b & [1] 18730 $ ./a status from open is 0 At line 7 of file a.f Fortran runtime error: Illegal seek status from open is 0 At line 8 of file b.f Fortran runtime error: End of file -- Summary: I/O with named pipes does not work Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jvdelisle at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30162
next reply other threads:[~2006-12-12 4:28 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-12 4:28 jvdelisle at gcc dot gnu dot org [this message] 2006-12-15 21:15 ` [Bug libfortran/30162] " tkoenig at gcc dot gnu dot org 2006-12-16 11:44 ` tkoenig at gcc dot gnu dot org 2006-12-16 21:34 ` tkoenig at gcc dot gnu dot org 2006-12-28 21:22 ` tkoenig at gcc dot gnu dot org 2006-12-28 21:39 ` tkoenig at gcc dot gnu dot org 2006-12-28 23:11 ` jvdelisle at gcc dot gnu dot org 2006-12-29 9:51 ` tkoenig at gcc dot gnu dot org 2007-01-01 4:59 ` jvdelisle at gcc dot gnu dot org 2007-01-01 15:17 ` tkoenig at gcc dot gnu dot org 2007-01-01 17:51 ` jvdelisle at gcc dot gnu dot org 2007-01-02 22:09 ` tkoenig at gcc dot gnu dot org 2007-01-05 5:00 ` patchapp at dberlin dot org 2007-01-06 0:14 ` jvdelisle at gcc dot gnu dot org 2007-01-06 21:08 ` jvdelisle at gcc dot gnu dot org 2007-01-06 22:27 ` tkoenig at gcc dot gnu dot org 2007-01-07 1:34 ` jvdelisle at gcc dot gnu dot org 2007-02-01 7:20 ` jvdelisle at gcc dot gnu dot org 2007-02-01 9:28 ` burnus at gcc dot gnu dot org 2007-02-02 2:00 ` jvdelisle at gcc dot gnu dot org 2007-08-18 19:07 ` dagurasu15 at hotmail dot com 2007-08-18 19:08 ` dagurasu15 at hotmail dot com 2007-08-18 19:39 ` jvdelisle at gcc dot gnu dot org 2007-08-19 19:46 ` 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-30162-10743@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: 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).