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 rtl-optimization/17088] poor fortran optimisation at -O2/3
Date: Tue, 02 May 2006 05:01:00 -0000 [thread overview]
Message-ID: <20060502050142.24656.qmail@sourceware.org> (raw)
In-Reply-To: <bug-17088-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-05-02 05:01 -------
With:
$ gfc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../main/configure --prefix=/home/jerry/gcc/usr
--enable-languages=c,fortran --disable-libmudflap
Thread model: posix
gcc version 4.2.0 20060424 (experimental)
$ gfc -O2 -march=pentium4 test-optimize.f90 <gfortran
$ ./a.out
4.440892098500626E-016
0.748046000000000 0.544034000000000
$ ifc -O2 test-optimize.f90 <intel
$ ./a.out
0.000000000000000E+000
0.460028000000000 0.436027000000000
Still a lot of room for improvement here. The bottom left number is time using
matmul and the right is time hardcoded.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17088
next parent reply other threads:[~2006-05-02 5:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-17088-6642@http.gcc.gnu.org/bugzilla/>
2006-05-02 5:01 ` jvdelisle at gcc dot gnu dot org [this message]
2007-07-03 18:15 ` jv244 at cam dot ac dot uk
2008-08-28 15:57 ` [Bug rtl-optimization/17088] [4.4 Regression] " jv244 at cam dot ac dot uk
2008-08-28 15:57 ` jv244 at cam dot ac dot uk
2008-08-28 16:09 ` jv244 at cam dot ac dot uk
2004-08-18 20:47 [Bug rtl-optimization/17088] New: poor optimisation at -O2/3 and -fnew-ra jv244 at cam dot ac dot uk
2005-01-03 12:20 ` [Bug rtl-optimization/17088] poor fortran optimisation at -O2/3 steven at gcc dot gnu dot org
2005-01-06 21:30 ` jv244 at cam dot ac dot uk
2005-01-06 21:39 ` pinskia at gcc dot gnu dot org
2005-01-17 15:33 ` pinskia at gcc dot gnu dot org
2005-04-07 7:25 ` pinskia 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=20060502050142.24656.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).