public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/56812] Simple loop is not SLP-vectorized after r196872 Date: Tue, 02 Apr 2013 13:20:00 -0000 [thread overview] Message-ID: <bug-56812-4-MhT9O6OFZY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56812-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56812 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2013-04-02 Ever Confirmed|0 |1 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> 2013-04-02 13:20:47 UTC --- It should not make a difference ... I see that vectorization is determined to be not profitable though: t.C:11: note: === vect_update_slp_costs_according_to_vf ===cost model: prologue peel iters set to vf/2.cost model: epilogue peel iters set to vf/2 because peeling for alignment is unknown. t.C:11: note: Cost model analysis: Vector inside of loop cost: 1 Vector prologue cost: 11 Vector epilogue cost: 2 Scalar iteration cost: 1 Scalar outside cost: 0 Vector outside cost: 13 prologue iterations: 2 epilogue iterations: 2 Calculated minimum iters for profitability: 17 but it's not vectorized with 4.8 either. -fno-vect-cost-model fixes this. Are you sure you attached the correct testcase?
next prev parent reply other threads:[~2013-04-02 13:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-02 11:21 [Bug tree-optimization/56812] New: " ysrumyan at gmail dot com 2013-04-02 11:22 ` [Bug tree-optimization/56812] " ysrumyan at gmail dot com 2013-04-02 11:41 ` ysrumyan at gmail dot com 2013-04-02 13:20 ` rguenth at gcc dot gnu.org [this message] 2013-04-02 13:27 ` ysrumyan at gmail dot com 2013-04-02 13:36 ` rguenth at gcc dot gnu.org 2013-04-02 14:06 ` rguenth at gcc dot gnu.org 2013-04-03 8:04 ` rguenth at gcc dot gnu.org 2013-04-04 9:35 ` schwab@linux-m68k.org 2013-04-04 9:45 ` rguenther at suse dot de 2013-04-04 17:24 ` schwab@linux-m68k.org 2013-04-07 13:36 ` dominiq at lps dot ens.fr 2013-04-08 14:03 ` ysrumyan at gmail dot com 2013-04-08 14:05 ` ysrumyan at gmail dot com 2013-04-08 15:04 ` rguenth at gcc dot gnu.org 2013-04-08 15:48 ` ysrumyan at gmail dot com
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-56812-4-MhT9O6OFZY@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).