public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/56935] New: Basic block is not SLP-vectorizeed after r197635. Date: Fri, 12 Apr 2013 13:58:00 -0000 [thread overview] Message-ID: <bug-56935-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56935 Bug #: 56935 Summary: Basic block is not SLP-vectorizeed after r197635. Classification: Unclassified Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: ysrumyan@gmail.com It looks that after cost model changing some performance opportunities were lost. It can be seen for the attached test-case: before this change t.c:29: note: Cost model analysis: Vector inside of basic block cost: 5 Vector prologue cost: 0 Vector epilogue cost: 0 Scalar cost of basic block: 6 t.c:29: note: Basic block will be vectorized using SLP after this change t.c:29: note: Cost model analysis: Vector inside of basic block cost: 5 Vector prologue cost: 1 Vector epilogue cost: 0 Scalar cost of basic block: 6 t.c:29: note: not vectorized: vectorization is not profitable. Note that this test was extracted from 253.perlbench (spec2000) for which we got -4.5% performance degradation on corei7 (with avx).
next reply other threads:[~2013-04-12 13:58 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-12 13:58 ysrumyan at gmail dot com [this message] 2013-04-12 14:01 ` [Bug tree-optimization/56935] " ysrumyan at gmail dot com 2013-04-15 10:27 ` rguenth at gcc dot gnu.org 2013-04-15 14:54 ` ysrumyan at gmail dot com 2013-04-16 7:48 ` rguenther at suse dot de 2013-04-22 14:47 ` rguenth 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-56935-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).