public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44931] For INPUT_UNIT, INQUIRE NAME= should not return "stdin"
Date: Wed, 04 Aug 2010 10:02:00 -0000 [thread overview]
Message-ID: <20100804100227.17000.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44931-14229@http.gcc.gnu.org/bugzilla/>
------- Comment #11 from burnus at gcc dot gnu dot org 2010-08-04 10:02 -------
(In reply to comment #10)
> Reply to comment #9.
>
> Yes, this is what I was thinking. I wanted to float the first step out there to
> see what else we would discover.
I think now that there are essentially no test suite failures (except some old
ones one more obscure targets), one could add a patch similar to the one in
comment 9...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44931
next prev parent reply other threads:[~2010-08-04 10:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 20:51 [Bug fortran/44931] New: " jkrahn at nc dot rr dot com
2010-07-14 15:44 ` [Bug fortran/44931] " burnus at gcc dot gnu dot org
2010-07-15 21:39 ` jkrahn at nc dot rr dot com
2010-07-15 21:49 ` jkrahn at nc dot rr dot com
2010-07-24 4:08 ` jvdelisle at gcc dot gnu dot org
2010-07-24 8:22 ` burnus at gcc dot gnu dot org
2010-07-25 0:48 ` jvdelisle at gcc dot gnu dot org
2010-07-29 1:32 ` jvdelisle at gcc dot gnu dot org
2010-07-29 8:26 ` burnus at gcc dot gnu dot org
2010-07-30 1:47 ` jvdelisle at gcc dot gnu dot org
2010-08-04 10:02 ` burnus at gcc dot gnu dot org [this message]
2010-08-14 18:59 ` jvdelisle at gcc dot gnu dot org
2010-08-17 3:14 ` jvdelisle at gcc dot gnu dot org
[not found] <bug-44931-4@http.gcc.gnu.org/bugzilla/>
2010-11-04 19:30 ` jb 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=20100804100227.17000.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).