This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libfortran/50016] The fortran program 's io is very slow


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50016

--- Comment #4 from PcX <xunxun1982 at gmail dot com> 2011-08-07 23:22:55 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.

Yea, I modify it as your follows, but it will also take a very long time (so I
break it when it runs more than 1 minute).
At the same time, gcc 4.5.3 will only take some seconds.

btw, I use Win7 64bit, the CRT is MinGW64 project's CRT.
But my gcc4.5.3 also use MinGW64 CRT, so I think that's the gcc4.6's reason,
not CRT's.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]