public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jpr at csc dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47583] [4.6 Regression] Inquire affected by previous read
Date: Wed, 02 Feb 2011 12:48:00 -0000 [thread overview]
Message-ID: <bug-47583-4-uhHK0cWQ5H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47583-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47583
--- Comment #7 from jpr at csc dot fi 2011-02-02 12:48:37 UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> Thanks a lot, at least for me this patch seems to solve the problem.
Well, that patch did break the direct_io_1.f90 test case however,
as the ext.dt member setting overwrote the ext.iterator member (when
there was implied do loop in the inquire(iolength=) statement).
This might be better:
Index: io.c
===================================================================
--- io.c (revision 169506)
+++ io.c (working copy)
@@ -3091,7 +3091,8 @@
cp = gfc_get_code ();
cp->op = EXEC_TRANSFER;
cp->expr1 = expr;
- cp->ext.dt = current_dt;
+ if (k != M_INQUIRE)
+ cp->ext.dt = current_dt;
*cpp = cp;
return MATCH_YES;
next prev parent reply other threads:[~2011-02-02 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 21:53 [Bug fortran/47583] New: " harald at klimachs dot de
2011-02-01 22:17 ` [Bug fortran/47583] " kargl at gcc dot gnu.org
2011-02-02 3:09 ` [Bug fortran/47583] [4.6 Regression] " jvdelisle at gcc dot gnu.org
2011-02-02 6:04 ` harald at klimachs dot de
2011-02-02 6:15 ` harald at klimachs dot de
2011-02-02 7:12 ` jpr at csc dot fi
2011-02-02 8:04 ` harald at klimachs dot de
2011-02-02 10:03 ` jakub at gcc dot gnu.org
2011-02-02 12:48 ` jpr at csc dot fi [this message]
2011-02-03 5:36 ` pault at gcc dot gnu.org
2011-02-09 5:31 ` jvdelisle at gcc dot gnu.org
2011-02-09 6:12 ` jvdelisle at gcc dot gnu.org
2011-02-09 6:37 ` jvdelisle at gcc dot gnu.org
2011-02-09 7:05 ` harald at klimachs dot de
2011-02-09 15:48 ` 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-47583-4-uhHK0cWQ5H@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).