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 target/34501] The vector cost model does not seem suited for Intel Core2Duo Date: Tue, 06 Dec 2011 11:46:00 -0000 [thread overview] Message-ID: <bug-34501-4-7H8Cp6qtPc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-34501-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34501 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-12-06 11:45:39 UTC --- Although I don't know if the cost model is perfectly tuned for the Intel Core2Duo, the particular instance of this PR has been fixed since a long time (see pr34265 and pr50904), on trunk at r182043, I now get on a slightly faster proc (2.5Ghz vs. 2.1Ghz): [macbook] lin/test% time gfc -O3 -ffast-math -funroll-loops induct.f90 7.969u 0.101s 0:08.07 99.8% 0+0k 0+40io 0pf+0w [macbook] lin/test% time a.out > /dev/null 13.062u 0.026s 0:13.09 99.9% 0+0k 0+0io 0pf+0w [macbook] lin/test% time gfc -O3 -ffast-math -funroll-loops induct.f90 --param min-vect-loop-bound=2 7.965u 0.110s 0:08.08 99.8% 0+0k 0+23io 0pf+0w [macbook] lin/test% time a.out > /dev/null 13.063u 0.027s 0:13.09 99.9% 0+0k 0+0io 0pf+0w So I am closing the PR as fixed. Thanks for all the work leading to a nice speed-up.
next parent reply other threads:[~2011-12-06 11:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-34501-4@http.gcc.gnu.org/bugzilla/> 2011-12-06 11:46 ` dominiq at lps dot ens.fr [this message] 2007-12-16 21:02 [Bug tree-optimization/34501] New: " dominiq at lps dot ens dot fr 2007-12-16 21:20 ` [Bug target/34501] " pinskia at gcc dot gnu dot org 2009-09-17 9:52 ` ubizjak at gmail dot com 2010-05-09 16:10 ` howarth at nitro dot med dot uc dot edu 2010-05-09 19:27 ` dirtyepic at gentoo dot org 2010-05-09 19:38 ` howarth at nitro dot med dot uc dot edu 2010-05-09 23:12 ` howarth at nitro dot med dot uc dot edu
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-34501-4-7H8Cp6qtPc@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: linkBe 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).