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/46010] I/O: Namelist-reading bug
Date: Wed, 13 Oct 2010 21:42:00 -0000 [thread overview]
Message-ID: <20101013214200.8bYcwAb8etf4klm49vXoSJznrV38LV0v_JJGsuXtt5Y@z> (raw)
In-Reply-To: <bug-46010-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46010
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
CC| |burnus at gcc dot gnu.org,
| |jvdelisle at gcc dot
| |gnu.org
Summary|reading of structure |I/O: Namelist-reading bug
Known to fail| |4.2.4, 4.6.0
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-10-13 21:42:19 UTC ---
Jerry, can you have a look?
The first 12 items look OK (cf. "fort.11") if one compiles with NAG or ifort.
With gfortran, the items 1 looks OK, two has garbage, three looks OK - but has
the short/long name belonging to item 2 etc.
next prev parent reply other threads:[~2010-10-13 21:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 20:59 [Bug fortran/46010] New: reading of structure marco at hulten dot org
2010-10-13 21:42 ` burnus at gcc dot gnu.org [this message]
2010-10-14 3:20 ` [Bug fortran/46010] I/O: Namelist-reading bug jvdelisle at gcc dot gnu.org
2010-10-14 3:33 ` jvdelisle at gcc dot gnu.org
2010-10-14 8:09 ` burnus at gcc dot gnu.org
2010-10-14 18:16 ` marco at hulten dot org
2010-10-14 19:13 ` jvdelisle at gcc dot gnu.org
2010-10-25 5:48 ` jvdelisle at gcc dot gnu.org
2010-10-25 13:12 ` jvdelisle at gcc dot gnu.org
2010-10-26 1:37 ` jvdelisle at gcc dot gnu.org
2010-10-26 9:13 ` marco at hulten dot org
2010-10-26 19:05 ` jvdelisle at gcc dot gnu.org
2010-10-26 19:34 ` jvdelisle at gcc dot gnu.org
2010-10-26 19:37 ` jvdelisle at gcc dot gnu.org
2010-11-02 20:29 ` marco at hulten dot org
2010-11-04 0:17 ` jvdelisle at gcc dot gnu.org
2010-11-04 0:25 ` jvdelisle at gcc dot gnu.org
2010-11-04 0:34 ` jvdelisle at gcc dot gnu.org
2010-11-04 0:38 ` jvdelisle at gcc dot gnu.org
2010-11-04 0:42 ` jvdelisle 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=20101013214200.8bYcwAb8etf4klm49vXoSJznrV38LV0v_JJGsuXtt5Y@z \
--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).