public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/50016] [4.7 Regression] Drastic I/O performance regression on Windows
Date: Wed, 09 Nov 2011 16:01:00 -0000 [thread overview]
Message-ID: <bug-50016-4-JUa2QAFTGv@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
--- Comment #19 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-11-09 15:46:20 UTC ---
Author: jb
Date: Wed Nov 9 15:46:15 2011
New Revision: 181207
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=181207
Log:
PR 50016 Slow I/O on MingW due to _commit
frontend ChangeLog:
2011-11-09 Janne Blomqvist <jb@gcc.gnu.org>
PR libfortran/50016
* gfortran.texi (Data consistency and durability): New section.
testsuite ChangeLog:
2011-11-09 Janne Blomqvist <jb@gcc.gnu.org>
PR libfortran/50016
* gfortran.dg/inquire_size.f90: Don't flush the unit.
libgfortran ChangeLog:
2011-11-09 Janne Blomqvist <jb@gcc.gnu.org>
PR libfortran/50016
* io/inquire.c (inquire_via_unit): Flush the unit and use ssize.
* io/unix.c (buf_flush): Don't call _commit.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/gfortran.texi
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/inquire_size.f90
trunk/libgfortran/ChangeLog
trunk/libgfortran/io/inquire.c
trunk/libgfortran/io/unix.c
next prev parent reply other threads:[~2011-11-09 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 17:13 [Bug libfortran/50016] New: The fortran program 's io is very slow 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
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 [this message]
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-JUa2QAFTGv@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).