public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ed at eh3 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24459] gfortran namelist regression
Date: Thu, 20 Oct 2005 19:53:00 -0000 [thread overview]
Message-ID: <20051020195306.5464.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24459-11560@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from ed at eh3 dot com 2005-10-20 19:53 -------
The same error happens using gcc from cvs today (2005-10-20).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
next prev parent reply other threads:[~2005-10-20 19:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 18:23 [Bug fortran/24459] New: " ed at eh3 dot com
2005-10-20 19:53 ` ed at eh3 dot com [this message]
2005-10-21 22:27 ` [Bug libfortran/24459] gfortran namelist problem pinskia at gcc dot gnu dot org
2005-10-26 2:44 ` jvdelisle at gcc dot gnu dot org
2005-10-30 2:59 ` jvdelisle at gcc dot gnu dot org
2005-11-02 6:41 ` jvdelisle at gcc dot gnu dot org
2005-11-02 13:12 ` ed at eh3 dot com
2005-11-24 7:21 ` jvdelisle at gcc dot gnu dot org
2005-11-24 16:26 ` ed at eh3 dot com
2005-11-24 17:25 ` jvdelisle at gcc dot gnu dot org
2005-11-25 19:44 ` jvdelisle at gcc dot gnu dot org
2005-12-04 19:54 ` ed at eh3 dot com
2005-12-04 23:11 ` jvdelisle at gcc dot gnu dot org
2006-04-22 23:23 ` jvdelisle at gcc dot gnu dot org
2006-05-02 0:02 ` jvdelisle at gcc dot gnu dot org
2006-05-02 16:21 ` ed at eh3 dot com
2006-05-15 19:30 ` patchapp at dberlin dot org
2006-05-20 7:15 ` jvdelisle at gcc dot gnu dot org
2006-05-20 7:20 ` [Bug libfortran/24459] [4.1 Only] " jvdelisle at gcc dot gnu dot org
2006-05-21 1:56 ` jvdelisle at gcc dot gnu dot org
2006-05-29 5:19 ` jvdelisle at gcc dot gnu dot org
2006-05-29 5:22 ` jvdelisle at gcc dot gnu dot org
2006-05-29 5:23 ` jvdelisle at gcc dot gnu dot org
2007-01-02 4:36 ` jvdelisle at gcc dot gnu dot org
2007-01-10 19:01 ` pinskia 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=20051020195306.5464.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).