public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tilo@tilo-schwarz.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55117] Programs fails to read namelist (contains derived types objects)
Date: Mon, 25 Feb 2013 19:02:00 -0000 [thread overview]
Message-ID: <bug-55117-4-9QiwkOUzeE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55117-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55117
--- Comment #16 from Tilo Schwarz <tilo@tilo-schwarz.de> 2013-02-25 19:01:50 UTC ---
(In reply to comment #14)
> Created attachment 29532 [details]
> Namelist patch
Bummer, I had a typo in the comment:
The second hunk should read
"/* Don't move first_nl" instead of
"/* Don't move pprev_nl":
@@ -2901,7 +2901,8 @@ get_name:
goto nml_err_ret;
}
- if (*pprev_nl == NULL || !component_flag)
+ /* Don't move first_nl further in the list if a qualifier was found */
+ if ((*pprev_nl == NULL && !qualifier_flag) || !component_flag)
first_nl = nl;
Sorry,
Tilo
next prev parent reply other threads:[~2013-02-25 19:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 14:31 [Bug fortran/55117] New: " pmarguinaud at hotmail dot com
2012-10-29 14:32 ` [Bug fortran/55117] " pmarguinaud at hotmail dot com
2012-10-29 14:34 ` pmarguinaud at hotmail dot com
2012-10-29 16:03 ` janus at gcc dot gnu.org
2012-10-31 19:53 ` burnus at gcc dot gnu.org
2013-01-04 2:54 ` w6ws at earthlink dot net
2013-01-04 14:33 ` w6ws at earthlink dot net
2013-01-04 16:59 ` kargl at gcc dot gnu.org
2013-01-04 17:22 ` w6ws at earthlink dot net
2013-01-05 19:16 ` jvdelisle at gcc dot gnu.org
2013-01-06 18:51 ` jvdelisle at gcc dot gnu.org
2013-02-22 20:58 ` tilo@tilo-schwarz.de
2013-02-22 22:40 ` tilo@tilo-schwarz.de
2013-02-24 0:28 ` tilo@tilo-schwarz.de
2013-02-25 1:00 ` tilo@tilo-schwarz.de
2013-02-25 1:03 ` tilo@tilo-schwarz.de
2013-02-25 19:02 ` tilo@tilo-schwarz.de [this message]
2013-02-25 19:49 ` mikael at gcc dot gnu.org
2013-02-25 20:29 ` tilo@tilo-schwarz.de
2013-03-22 10:10 ` burnus at gcc dot gnu.org
2013-03-30 3:54 ` jvdelisle at gcc dot gnu.org
2013-03-30 5:05 ` jvdelisle at gcc dot gnu.org
2013-04-25 12:42 ` burnus at gcc dot gnu.org
2013-06-16 18:04 ` dominiq at lps dot ens.fr
2014-03-23 23:20 ` jvdelisle at gcc dot gnu.org
2014-05-26 15:20 ` jvdelisle at gcc dot gnu.org
2014-05-26 15:33 ` jvdelisle at gcc dot gnu.org
2014-06-07 17:42 ` jvdelisle at gcc dot gnu.org
2014-06-07 17:43 ` 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=bug-55117-4-9QiwkOUzeE@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).