From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-365035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 5354 invoked by alias); 7 Aug 2011 23:23:30 -0000
Received: (qmail 5346 invoked by uid 22791); 7 Aug 2011 23:23:29 -0000
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00,TW_NX
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 07 Aug 2011 23:23:16 +0000
From: "xunxun1982 at gmail 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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xunxun1982 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-50016-4-FiHCx2uchL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50016-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50016-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Date: Sun, 07 Aug 2011 23:23:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-08/txt/msg00809.txt.bz2

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.