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 fortran/56981] Slow I/O: Unformatted 5x slower, large sys component; formatted slow as well
Date: Tue, 16 Apr 2013 15:20:00 -0000 [thread overview]
Message-ID: <bug-56981-4-CAlwVe9ikU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56981-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56981
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-04-16 15:20:20 UTC ---
For unformatted pathf95 and g95 have (top 10 entries of strace):
3 brk 4 close
3 getrlimit 4 ioctl
8 read 4 rt_sigaction
10 close 6 fstat
13 fstat 6 mprotect
20 mprotect 7 brk
21 stat 10 mmap
22 mmap 17 stat
46 open 23 open
367 write 734 write
gfortran has the following syscalls, which are at least invoked twice:
3 brk
5 read
7 close
10 rt_sigaction
11 access
11 fstat
12 mprotect
16 stat
18 mmap
26 open
2000000 lseek
4000000 write
next parent reply other threads:[~2013-04-16 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-56981-4@http.gcc.gnu.org/bugzilla/>
2013-04-16 15:20 ` burnus at gcc dot gnu.org [this message]
2013-04-17 0:58 ` jvdelisle at gcc dot gnu.org
2013-04-17 10:50 ` jb at gcc dot gnu.org
2013-04-17 14:50 ` burnus at gcc dot gnu.org
2013-04-18 1:21 ` jvdelisle at gcc dot gnu.org
2013-04-19 10:34 ` jb at gcc dot gnu.org
2013-04-29 9:35 ` burnus at gcc dot gnu.org
2013-04-29 9:36 ` burnus at gcc dot gnu.org
2013-12-21 20:15 ` dominiq at lps dot ens.fr
2014-06-08 18:08 ` jvdelisle at gcc dot gnu.org
2014-06-08 23:57 ` jvdelisle 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-56981-4-CAlwVe9ikU@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).