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 libfortran/59727] [4.7/4.8/4.9 Regression] reading from character string returns end of file
Date: Fri, 14 Mar 2014 05:08:00 -0000 [thread overview]
Message-ID: <bug-59727-4-432uWQEh8P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59727-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59727
--- Comment #9 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Jerry DeLisle from comment #8)
> The patch committed as shown in comment #42 of pr38199 appears to fix this
> one incidentally. Regarding comment 5, I am still not sure the code is
> valid, but I do agree there is no reason to give an error either. I will be
> looking at a few other issues related to this and will close the PR when we
> are confident there is not something else lurking here. See also PR58324
I can confirm this bug is fixed on trunk. I also have a patch posted for
PR58324 which demonstrates they were really one in the same bug related to how
and when eat_line was being used.
next prev parent reply other threads:[~2014-03-14 5:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 18:12 [Bug libfortran/59727] New: " dms35 at cornell dot edu
2014-01-08 21:15 ` [Bug libfortran/59727] [4.7/4.8/4.9 Regression] " dominiq at lps dot ens.fr
2014-01-09 0:26 ` kargl at gcc dot gnu.org
2014-01-10 17:55 ` dms35 at cornell dot edu
2014-01-11 4:12 ` jvdelisle at gcc dot gnu.org
2014-01-31 10:49 ` rguenth at gcc dot gnu.org
2014-03-13 5:24 ` jvdelisle at gcc dot gnu.org
2014-03-13 5:36 ` jvdelisle at gcc dot gnu.org
2014-03-14 5:08 ` jvdelisle at gcc dot gnu.org [this message]
2014-03-16 0:48 ` dominiq at lps dot ens.fr
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-59727-4-432uWQEh8P@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).