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 middle-end/41115] Tree-vectorizer: VecCost tuning for X2: Without vectorization 30% faster
Date: Thu, 28 Mar 2013 23:08:00 -0000 [thread overview]
Message-ID: <bug-41115-4-WrtCGSzDzV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41115-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41115
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-28 23:08:00 UTC ---
(In reply to comment #3)
> It would be nice to see where we are today with respect to the cost model /
> vectorizing / not vectorizing.
Answer: It became much worse (compared to GCC 4.5 of comment 0):
Using gcc version 4.8.0 20130308 [trunk revision 196547], the induct runtimes
are:
gfortran -march=native -ffast-math -O3 -ftree-vectorize -fvect-cost-model
induct.f90
real 0m47.142s / user 0m47.072s / sys 0m0.020s
gfortran-4.8 -march=native -ffast-math -O3 -ftree-vectorize
-fno-vect-cost-model induct.f90
real 0m35.713s / user 0m35.236s / sys 0m0.052s
time gfortran-4.8 -march=native -ffast-math -O3 -fno-tree-vectorize induct.f90
real 0m47.837s / user 0m47.388s / sys 0m0.028s
real 0m47.514s / user 0m47.428s / sys 0m0.044s
gfortran -march=opteron -ffast-math -funroll-loops -fno-tree-vectorize
-ftree-loop-linear -msse3 -O3 induct.f90
real 0m44.676s / user 0m44.640s / sys 0m0.032s
gfortran-4.5 -march=opteron -ffast-math -funroll-loops -fno-tree-vectorize
-ftree-loop-linear -msse3 -O3 induct.f90; time ./a.out
real 0m34.591s / user 0m34.524s / sys 0m0.020s
prev parent reply other threads:[~2013-03-28 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41115-4@http.gcc.gnu.org/bugzilla/>
2012-07-13 8:37 ` rguenth at gcc dot gnu.org
2012-11-13 18:44 ` ubizjak at gmail dot com
2013-03-27 12:38 ` rguenth at gcc dot gnu.org
2013-03-28 23:08 ` burnus at gcc dot gnu.org [this message]
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-41115-4-WrtCGSzDzV@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).