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/60148] strings in NAMELIST do not honor DELIM= in open statement Date: Fri, 21 Mar 2014 22:20:00 -0000 [thread overview] Message-ID: <bug-60148-4-g1m6BvGjvB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60148-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60148 --- Comment #15 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- Author: jvdelisle Date: Fri Mar 21 22:19:44 2014 New Revision: 208759 URL: http://gcc.gnu.org/viewcvs?rev=208759&root=gcc&view=rev Log: 2014-03-21 Jerry DeLisle <jvdelisle@gcc.gnu> PR libfortran/60148 * io/transfer.c (data_transfer_init): If std= was specified, set delim status to DELIM_NONE of no other was specified. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/transfer.c
next prev parent reply other threads:[~2014-03-21 22:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-11 16:15 [Bug fortran/60148] New: " kargl at gcc dot gnu.org 2014-02-11 16:30 ` [Bug fortran/60148] " kargl at gcc dot gnu.org 2014-02-11 18:28 ` dominiq at lps dot ens.fr 2014-02-12 2:34 ` jvdelisle at gcc dot gnu.org 2014-02-12 3:12 ` kargl at gcc dot gnu.org 2014-02-12 5:24 ` sgk at troutmask dot apl.washington.edu 2014-02-13 2:26 ` jvdelisle at gcc dot gnu.org 2014-02-23 19:56 ` jvdelisle at gcc dot gnu.org 2014-02-23 21:07 ` burnus at gcc dot gnu.org 2014-02-26 5:47 ` jvdelisle at gcc dot gnu.org 2014-03-04 4:34 ` jvdelisle at gcc dot gnu.org 2014-03-04 5:46 ` jvdelisle at gcc dot gnu.org 2014-03-08 21:57 ` jvdelisle at gcc dot gnu.org 2014-03-21 22:15 ` jvdelisle at gcc dot gnu.org 2014-03-21 22:20 ` jvdelisle at gcc dot gnu.org [this message] 2014-03-21 22:26 ` 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-60148-4-g1m6BvGjvB@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).