public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31139] sum(w_re(1:nn,1)*fi(i(1:nn, ii))) up to 3.5x slower than C version
Date: Sat, 22 Jun 2013 16:55:00 -0000 [thread overview]
Message-ID: <bug-31139-4-Gj65i2j5Az@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31139-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31139
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I have not tested this with latest trunk, but I wonder if any of the recent
> optimization work has improved this. Can it be closed yet?
A quick test on a 2.5Ghz Core2Duo at revision 200321 with -Ofast shows
Fortran: 0.330040932
c_sse: 0.225150943
c_struct: 0.227035046
and with -Ofast -funroll-loops
Fortran: 0.213014960
c_sse: 0.223238945
c_struct: 0.209081888
The change occured between 4.5 and 4.6 (note that 4.6 and 4.7 gives 0.263675928
without -funroll-loops). Is this still an issue?
next parent reply other threads:[~2013-06-22 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31139-4@http.gcc.gnu.org/bugzilla/>
2013-06-22 16:55 ` dominiq at lps dot ens.fr [this message]
2015-10-10 9:21 ` dominiq at lps dot ens.fr
2007-03-11 22:38 [Bug fortran/31139] New: " burnus at gcc dot gnu dot org
2007-03-11 22:45 ` [Bug fortran/31139] " burnus at gcc dot gnu dot org
2007-03-11 22:50 ` burnus at gcc dot gnu dot org
2007-03-12 5:33 ` pinskia at gcc dot gnu dot org
2007-03-12 5:38 ` pinskia at gcc dot gnu dot org
2007-03-12 7:58 ` burnus at gcc dot gnu dot org
2007-03-12 8:16 ` burnus at gcc dot gnu dot org
2007-04-18 5:56 ` fxcoudert at gcc dot gnu dot org
2010-09-12 15:45 ` jvdelisle at gcc dot gnu dot 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-31139-4-Gj65i2j5Az@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).