public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cgl_lgs at 163 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/50016] The fortran program 's io is very slow
Date: Tue, 09 Aug 2011 07:47:00 -0000 [thread overview]
Message-ID: <bug-50016-4-yCeBhmlOaF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50016-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50016
好小爱新 <cgl_lgs at 163 dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cgl_lgs at 163 dot com
--- Comment #11 from 好小爱新 <cgl_lgs at 163 dot com> 2011-08-09 07:46:28 UTC ---
(In reply to comment #3)
> I can not reproduce this on my system. I did notice a warning about line
> truncation on the long line in the example. You may want to use line
> continuations for that one like this:
>
> write(13,rec=jj*i+j)nlgs(1,j,i),dlgs(200,j,i),nlgs(2,j,i),dlgs(199,j,i),&
> & nlgs(3,j,i),dlgs(198,j,i),nlgs(4,j,i),dlgs(197,j,i),nlgs(5:8,j,i),&
> & dlgs(154:190,j,i)
>
> Sometimes if you get truncated in just the right place, the program will still
> compile and run, but not the way you think it is.
you can compile it using "-ffree-line-length-none":)
next prev parent reply other threads:[~2011-08-09 7:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 17:13 [Bug libfortran/50016] New: " xunxun1982 at gmail dot com
2011-08-07 17:14 ` [Bug libfortran/50016] " xunxun1982 at gmail dot com
2011-08-07 17:17 ` xunxun1982 at gmail dot com
2011-08-07 23:06 ` jvdelisle at gcc dot gnu.org
2011-08-07 23:23 ` xunxun1982 at gmail dot com
2011-08-07 23:25 ` xunxun1982 at gmail dot com
2011-08-08 11:52 ` jb at gcc dot gnu.org
2011-08-08 12:06 ` xunxun1982 at gmail dot com
2011-08-08 12:36 ` xunxun1982 at gmail dot com
2011-08-08 12:39 ` xunxun1982 at gmail dot com
2011-08-08 13:03 ` xunxun1982 at gmail dot com
2011-08-09 7:47 ` cgl_lgs at 163 dot com [this message]
2011-08-12 16:21 ` jvdelisle at gcc dot gnu.org
2011-10-14 10:29 ` [Bug libfortran/50016] [4.6/4.7 Regression] Drastic I/O performance regression on Windows burnus at gcc dot gnu.org
2011-10-18 13:00 ` burnus at gcc dot gnu.org
2011-10-18 13:09 ` [Bug libfortran/50016] [4.7 " burnus at gcc dot gnu.org
2011-10-18 13:22 ` xunxun1982 at gmail dot com
2011-10-19 17:30 ` burnus at gcc dot gnu.org
2011-10-20 6:50 ` xunxun1982 at gmail dot com
2011-11-09 16:01 ` jb at gcc dot gnu.org
2011-11-18 11:47 ` jb 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-50016-4-yCeBhmlOaF@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).