public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47778] reading two arrays of structures from namelist fails Date: Mon, 07 Mar 2011 02:06:00 -0000 [thread overview] Message-ID: <bug-47778-4-k7M9LLuoHs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47778-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47778 --- Comment #9 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2011-03-07 02:06:32 UTC --- Author: jvdelisle Date: Mon Mar 7 02:06:27 2011 New Revision: 170726 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170726 Log: 2011-03-06 Jerry DeLisle <jvdelisle@gcc.gnu.org> PR libgfortran/47778 * io/list_read.c (namelist_read): Intialize the error string buffere. If pprev_nl was used during the previous namelist read and the rank was zero, reset the pointer to NULL for the next namelist read. Modified: branches/gcc-4_5-branch/libgfortran/ChangeLog branches/gcc-4_5-branch/libgfortran/io/list_read.c
next prev parent reply other threads:[~2011-03-07 2:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-17 10:01 [Bug fortran/47778] New: " arnold.moene at wur dot nl 2011-02-17 11:00 ` [Bug fortran/47778] " burnus at gcc dot gnu.org 2011-02-17 19:31 ` jvdelisle at gcc dot gnu.org 2011-02-19 16:40 ` jvdelisle at gcc dot gnu.org 2011-02-21 14:45 ` jvdelisle at gcc dot gnu.org 2011-02-27 8:13 ` jvdelisle at gcc dot gnu.org 2011-02-27 20:10 ` jvdelisle at gcc dot gnu.org 2011-02-27 20:13 ` jvdelisle at gcc dot gnu.org 2011-02-27 20:16 ` jvdelisle at gcc dot gnu.org 2011-03-07 2:06 ` jvdelisle at gcc dot gnu.org [this message] 2011-03-07 2:12 ` jvdelisle at gcc dot gnu.org 2011-03-07 2:16 ` 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-47778-4-k7M9LLuoHs@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: linkBe 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).