public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/37707] Namelist read of array of derived type incorrect Date: Sun, 19 Oct 2008 15:31:00 -0000 [thread overview] Message-ID: <20081019152952.7999.qmail@sourceware.org> (raw) In-Reply-To: <bug-37707-109@http.gcc.gnu.org/bugzilla/> ------- Comment #23 from jvdelisle at gcc dot gnu dot org 2008-10-19 15:29 ------- Subject: Bug 37707 Author: jvdelisle Date: Sun Oct 19 15:28:25 2008 New Revision: 141227 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=141227 Log: 2008-10-19 Jerry DeLisle <jvdelisle@gcc.gnu.org PR libfortran/37863 Backport from trunk. * io/write_float.def (WRITE_FLOAT): Round to 1.0 correctly. 2008-10-19 Jerry DeLisle <jvdelisle@gcc.gnu.org PR libfortran/37707 Backport from trunk. * io/list_read.c (nml_get_obj_data): If the first namelist object rank is greater than zero, call nml_object_read with the first object rather than the sub-object. Modified: branches/gcc-4_3-branch/libgfortran/ChangeLog branches/gcc-4_3-branch/libgfortran/io/list_read.c branches/gcc-4_3-branch/libgfortran/io/write_float.def -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37707
next prev parent reply other threads:[~2008-10-19 15:31 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-01 21:01 [Bug libfortran/37707] New: " toon at moene dot indiv dot nluug dot nl 2008-10-01 21:43 ` [Bug libfortran/37707] " burnus at gcc dot gnu dot org 2008-10-02 1:48 ` jvdelisle at gcc dot gnu dot org 2008-10-09 2:41 ` jvdelisle at gcc dot gnu dot org 2008-10-09 4:05 ` jvdelisle at gcc dot gnu dot org 2008-10-09 4:17 ` jvdelisle at gcc dot gnu dot org 2008-10-09 9:16 ` pault at gcc dot gnu dot org 2008-10-09 9:28 ` dominiq at lps dot ens dot fr 2008-10-09 13:33 ` burnus at gcc dot gnu dot org 2008-10-10 2:12 ` jvdelisle at gcc dot gnu dot org 2008-10-10 2:15 ` jvdelisle at gcc dot gnu dot org 2008-10-18 5:26 ` jvdelisle at gcc dot gnu dot org 2008-10-18 5:37 ` jvdelisle at gcc dot gnu dot org 2008-10-18 8:44 ` toon at moene dot indiv dot nluug dot nl 2008-10-18 8:48 ` toon at moene dot indiv dot nluug dot nl 2008-10-18 8:48 ` toon at moene dot indiv dot nluug dot nl 2008-10-18 14:35 ` burnus at gcc dot gnu dot org 2008-10-18 14:54 ` burnus at gcc dot gnu dot org 2008-10-18 15:14 ` burnus at gcc dot gnu dot org 2008-10-18 15:34 ` toon at moene dot indiv dot nluug dot nl 2008-10-18 17:48 ` jvdelisle at gcc dot gnu dot org 2008-10-18 21:49 ` jvdelisle at gcc dot gnu dot org 2008-10-19 9:46 ` burnus at gcc dot gnu dot org 2008-10-19 15:31 ` jvdelisle at gcc dot gnu dot org [this message] 2008-10-19 15:33 ` jvdelisle at gcc dot gnu dot org 2008-10-19 15:41 ` jvdelisle at gcc dot gnu dot org 2008-10-19 16:12 ` toon at moene dot indiv dot nluug dot nl 2008-10-19 18:17 ` jvdelisle at gcc dot gnu dot org 2008-10-22 8:30 ` toon at moene dot indiv dot nluug dot nl 2008-10-23 2:33 ` jvdelisle at gcc dot gnu dot org 2008-10-23 2:45 ` jvdelisle at gcc dot gnu dot org 2008-10-23 2:51 ` jvdelisle at gcc dot gnu dot org 2008-10-23 6:20 ` burnus at gcc dot gnu dot org 2008-10-29 4:47 ` jvdelisle at gcc dot gnu dot org 2008-10-29 4:49 ` jvdelisle at gcc dot gnu dot org 2008-10-29 4:50 ` jvdelisle 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=20081019152952.7999.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: 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).