public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus 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, 19 Oct 2011 17:30:00 -0000	[thread overview]
Message-ID: <bug-50016-4-ZX2DVhB6r7@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 #17 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-10-19 17:27:08 UTC ---
Author: burnus
Date: Wed Oct 19 17:27:03 2011
New Revision: 180199

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=180199
Log:
2011-10-19  Janne Blomqvist  <jb@gcc.gnu.org>
            Kai Tietz  <ktietz@redhat.com>
            Tobias Burnus  <burnus@net-b.de>

        PR fortran/50016
        * io/unix.h (flush_sync): Add new libgfortran-internal
        * prototype.
        * io/unix.c (flush_sync): New function, which calls sflush and
        on MinGW(-w64) also _commit.
        (flush_all_units, flush_all_units_1): Replace sflush/_commit by
        flush_sync.
        * io/file_pos.c (st_flush): Replace sflush/_commit by
        * flush_sync.
        * io/intrinsics.c (flush_i4, flush_i8): Ditto.


Modified:
    branches/gcc-4_6-branch/libgfortran/ChangeLog
    branches/gcc-4_6-branch/libgfortran/io/file_pos.c
    branches/gcc-4_6-branch/libgfortran/io/intrinsics.c
    branches/gcc-4_6-branch/libgfortran/io/unix.c
    branches/gcc-4_6-branch/libgfortran/io/unix.h


  parent reply	other threads:[~2011-10-19 17:30 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 [this message]
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-ZX2DVhB6r7@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).