public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/50969] 17% degradation in 168.wupwise for interleave via permutation
Date: Wed, 02 Nov 2011 21:38:00 -0000	[thread overview]
Message-ID: <bug-50969-4-Uni39NS56j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50969-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50969

--- Comment #1 from Pat Haugen <pthaugen at gcc dot gnu.org> 2011-11-02 21:38:28 UTC ---
I swapped the numbers, should be:

-m64 -O3 -mcpu=power7
zaxpy : -79%
zscal : -24%

-m64 -O3 -mcpu=power7 -funroll-loops
zaxpy : -61%
zscal : -65%


  reply	other threads:[~2011-11-02 21:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 21:27 [Bug tree-optimization/50969] New: " pthaugen at gcc dot gnu.org
2011-11-02 21:38 ` pthaugen at gcc dot gnu.org [this message]
2011-11-03  8:19 ` [Bug tree-optimization/50969] " rguenth at gcc dot gnu.org
2012-02-06 21:40 ` wschmidt at gcc dot gnu.org
2012-02-06 21:43 ` wschmidt at gcc dot gnu.org
2012-02-14 19:42 ` wschmidt at gcc dot gnu.org
2012-03-02 14:54 ` wschmidt 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=bug-50969-4-Uni39NS56j@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).