public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49597] gfortran namelist read bug
Date: Wed, 27 Jul 2011 07:06:00 -0000 [thread overview]
Message-ID: <bug-49597-4-fz8lZsjj3F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49597-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49597
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
Known to work| |4.4.6, 4.5.2, 4.6.0, 4.7.0
Known to fail| |4.1.2, 4.5.1
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-07-27 07:05:22 UTC ---
(In reply to comment #2)
> I will tke this one.
Jerry: Judging from comment 1, it is already fixed for 4.4, 4.5 and 4.6/4.7.
Thus, I think no action is required.
David: Thanks for the bugreport. Can you try a newer version of gfortran? Your
Linux distribution might offer a new release (4.5.2 seems to be sufficient) -
alternatively, you could try the ones at
http://gcc.gnu.org/wiki/GFortranBinaries
next prev parent reply other threads:[~2011-07-27 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 19:03 [Bug fortran/49597] New: " david.sagan at gmail dot com
2011-06-30 19:32 ` [Bug fortran/49597] " dominiq at lps dot ens.fr
2011-07-26 21:00 ` jvdelisle at gcc dot gnu.org
2011-07-27 7:06 ` burnus at gcc dot gnu.org [this message]
2011-07-27 13:44 ` david.sagan at gmail dot com
2011-07-27 14:18 ` 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=bug-49597-4-fz8lZsjj3F@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: 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).