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/60810] [4.7/4.8/4.9/4.10 Regression] list directed io from array results in end of file
Date: Fri, 11 Apr 2014 19:41:00 -0000 [thread overview]
Message-ID: <bug-60810-4-LXhQ01C7DO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60810-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60810
--- Comment #4 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #3)
> The libgfortran change is in all of 4.7/4.8 branches and the trunk now I
> believe.
I am checking now. If so I will probably revert that previous patch.
next prev parent reply other threads:[~2014-04-11 19:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 17:31 [Bug fortran/60810] New: [4.9 " orion at cora dot nwra.com
2014-04-11 1:55 ` [Bug fortran/60810] " jvdelisle at gcc dot gnu.org
2014-04-11 5:35 ` jakub at gcc dot gnu.org
2014-04-11 9:08 ` rguenth at gcc dot gnu.org
2014-04-11 9:12 ` [Bug fortran/60810] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2014-04-11 9:12 ` jakub at gcc dot gnu.org
2014-04-11 19:41 ` jvdelisle at gcc dot gnu.org [this message]
2014-04-11 20:18 ` [Bug fortran/60810] [4.7/4.8/4.9/4.10 " jvdelisle at gcc dot gnu.org
2014-04-11 21:54 ` jvdelisle at gcc dot gnu.org
2014-04-12 0:05 ` jvdelisle at gcc dot gnu.org
2014-04-12 0:06 ` jvdelisle at gcc dot gnu.org
2014-04-12 18:42 ` jvdelisle at gcc dot gnu.org
2014-04-12 18:51 ` jvdelisle at gcc dot gnu.org
2014-04-13 2:10 ` jvdelisle at gcc dot gnu.org
2014-04-16 15:20 ` orion at cora dot nwra.com
2014-04-29 3:14 ` jvdelisle at gcc dot gnu.org
2014-04-29 3:15 ` 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-60810-4-LXhQ01C7DO@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).