public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dagurasu15 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/30162] I/O with named pipes does not work
Date: Sat, 18 Aug 2007 19:08:00 -0000	[thread overview]
Message-ID: <20070818190803.26290.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30162-10743@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from dagurasu15 at hotmail dot com  2007-08-18 19:08 -------
(In reply to comment #18)
> I think this is the same bug.  If not let me know and I'll repost it.
> This is a real bummer.  I use this to turn off noise from routines I don't have
> control of (and I mean ALOT of noise).  Maybe there is another way to do what I
> want though.  Anyway, the following produces a seek error on the write line. 
> It worked well in f77.  Now using gcc-4.1.2
> 
>        program bug
>         close(6)
>         open(6,file='/dev/null',status='old')
>         close(6)
> c  would normally do some noisy stuff here 
> c    but not needed to make the bug.
>         open(6,file='/dev/stdout',status='old')
>         write (*,*)"Hello"
>        end
> 

of course the comment should be one line higher.


-- 


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


  parent reply	other threads:[~2007-08-18 19:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12  4:28 [Bug libfortran/30162] New: " jvdelisle at gcc dot gnu dot org
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 [this message]
2007-08-18 19:39 ` jvdelisle at gcc dot gnu dot org
2007-08-19 19:46 ` jvdelisle at gcc dot gnu dot org
     [not found] <bug-30162-4@http.gcc.gnu.org/bugzilla/>
2012-08-02 17:34 ` iliev at rz dot rwth-aachen.de
2012-08-03 19:45 ` jb at gcc dot gnu.org
2012-08-06 13:43 ` burnus at gcc dot gnu.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=20070818190803.26290.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).