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 target/57796] AVX2 gather vectorization: code bloat and reduction of performance
Date: Fri, 05 Jul 2013 14:14:00 -0000	[thread overview]
Message-ID: <bug-57796-4-eI5mRXS6CI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57796-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Yuri Rumyantsev <ysrumyan at gmail dot com> ---
(In reply to Jakub Jelinek from comment #3)
> By tuning I've meant the vectorizer cost model.  If the desirability of
> gathers vs. no vectorization at all doesn't depend only on the insns in the
> loop, but also on how many iterations the loop has, then perhaps we'd need
> to runtime version it or something.

Jakub,

We have runtime versioning but for original bench vectorized version of loop is
 selected to execute, but if we change lower bound to 0 (as I did) scalar
version of loop is run.


  parent reply	other threads:[~2013-07-05 14:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  8:56 [Bug tree-optimization/57796] New: " vincenzo.innocente at cern dot ch
2013-07-03  9:33 ` [Bug tree-optimization/57796] " jakub at gcc dot gnu.org
2013-07-05 13:31 ` [Bug target/57796] " ysrumyan at gmail dot com
2013-07-05 13:49 ` jakub at gcc dot gnu.org
2013-07-05 14:14 ` ysrumyan at gmail dot com [this message]
2014-06-19  8:17 ` vincenzo.innocente at cern dot ch
2015-04-10 11:16 ` 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-57796-4-eI5mRXS6CI@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).