public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kirill.yukhin at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/50480] New: 10% performance regression on Spec2006 410.bwaves Date: Thu, 22 Sep 2011 10:26:00 -0000 [thread overview] Message-ID: <bug-50480-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50480 Bug #: 50480 Summary: 10% performance regression on Spec2006 410.bwaves Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: kirill.yukhin@intel.com Hi, Recently Richard fixed this http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49957 According to my measurements, fix for that bug caused (on Spec2006): For SandyBride CPU: * 410.bwaves degradation is -9.54% for peak32 * 410.bwaves degradation is -6.91% for base32 * 410.bwaves improvement is 1.00% for peak64 * 410.bwaves improvement is 0.91% 3or base64 For Corei7 CPU: * 410.bwaves degradation is -3.91% for peak32 * 410.bwaves degradation is -3.91% for base32 * 410.bwaves improvement is 1.94% for peak64 * 410.bwaves improvement is 3.23% 3or base64 For AMD (Phenom(tm) II X3 B75) CPU: * 410.bwaves degradation is -7.32% for peak32 * 410.bwaves degradation is -6.56% for base32 * 410.bwaves improvement is 2.01% for peak64 * 410.bwaves degradation is -1.34% 3or base64
next reply other threads:[~2011-09-22 10:00 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-22 10:26 kirill.yukhin at intel dot com [this message] 2011-09-22 10:29 ` [Bug tree-optimization/50480] " kirill.yukhin at intel dot com 2011-09-22 10:49 ` kirill.yukhin at intel dot com 2011-09-25 11:59 ` rguenth at gcc dot gnu.org 2011-09-27 8:49 ` kirill.yukhin at intel dot com 2011-09-27 9:00 ` rguenther at suse dot de 2012-04-20 23:29 ` meissner 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-50480-4@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).