public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/38654] Fortran I/O speedup
Date: Sun, 28 Dec 2008 20:56:00 -0000 [thread overview]
Message-ID: <20081228205511.22409.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38654-10391@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from jvdelisle at gcc dot gnu dot org 2008-12-28 20:55 -------
Daniel, it can't hurt to look.
Also, I have a format data hashing/caching patch in the works. This avoids
re-parsing format strings if they have already been parsed once such as in a
loop containing I/O statements. Preliminary results I am seeing about a 17%
speedup on at least one test case. The patch is fairly straightforward, but I
do need to find a Gnu-able hash function. I am using one out of wikipedia at
the moment. I will post the patch as soon as I get it to a bug free state.
Proof of principle is there for this.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38654
next prev parent reply other threads:[~2008-12-28 20:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 17:12 [Bug libfortran/38654] New: " tkoenig at gcc dot gnu dot org
2008-12-28 17:39 ` [Bug libfortran/38654] " domob at gcc dot gnu dot org
2008-12-28 20:56 ` jvdelisle at gcc dot gnu dot org [this message]
2008-12-28 21:03 ` jvdelisle at gcc dot gnu dot org
2008-12-28 21:28 ` domob at gcc dot gnu dot org
2008-12-29 12:26 ` tkoenig at gcc dot gnu dot org
2009-03-29 19:50 ` domob at gcc dot gnu dot org
2009-04-05 20:14 ` jvdelisle at gcc dot gnu dot org
2009-04-05 20:23 ` jvdelisle at gcc dot gnu dot org
2009-05-27 1:23 ` jvdelisle at gcc dot gnu dot org
2009-06-09 3:22 ` jvdelisle at gcc dot gnu dot org
[not found] <bug-38654-4@http.gcc.gnu.org/bugzilla/>
2021-12-26 5:51 ` pinskia 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=20081228205511.22409.qmail@sourceware.org \
--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).