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 middle-end/64909] [4.8/5 regression] Missed vectorization
Date: Mon, 09 Feb 2015 14:50:00 -0000	[thread overview]
Message-ID: <bug-64909-4-uaNLJXBKyg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64909-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64909

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #5)
> E.g.
> unsigned short a[32];
> unsigned int b[32];
> 
> void
> foo ()
> {
>   b[0] = a[0];
>   b[1] = a[1];
>   b[2] = a[2];
>   b[3] = a[3];
> }
> 
> will do, or b[0] = a[0] + 5; b[1] = a[1] + 5; b[2] = a[2] + 5; b[3] = a[3] +
> 5;
> and similar.

So it first of all boils down to the vectorizer not handling vectors of
different
size (V4HI and V4SI) at the same time.  The same thing happens when you
vectorize
double<->int conversion (for which there is already a bug somewhere).  For loop
vectorization this usually causes unnecessary unrolling (though that may be
profitable in the end).


  parent reply	other threads:[~2015-02-09 14:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 21:55 [Bug middle-end/64909] New: " hubicka at gcc dot gnu.org
2015-02-02 21:57 ` [Bug middle-end/64909] " hubicka at gcc dot gnu.org
2015-02-02 23:43 ` hjl.tools at gmail dot com
2015-02-09  0:07 ` pinskia at gcc dot gnu.org
2015-02-09 13:57 ` jakub at gcc dot gnu.org
2015-02-09 14:26 ` rguenth at gcc dot gnu.org
2015-02-09 14:38 ` jakub at gcc dot gnu.org
2015-02-09 14:50 ` rguenth at gcc dot gnu.org [this message]
2015-02-09 21:56 ` [Bug middle-end/64909] " jakub at gcc dot gnu.org
2015-02-09 22:05 ` hubicka at gcc dot gnu.org
2015-02-10  8:50 ` [Bug target/64909] [4.8/4.9/5 Regression] Missed vectorization with bdver1 rguenth at gcc dot gnu.org
2015-02-10  9:09 ` rguenth at gcc dot gnu.org
2015-02-10 11:49 ` [Bug tree-optimization/64909] " rguenth at gcc dot gnu.org
2015-02-10 11:50 ` [Bug tree-optimization/64909] [4.8/4.9 " rguenth at gcc dot gnu.org
2015-02-23 12:14 ` rguenth at gcc dot gnu.org
2015-04-04 10:47 ` [Bug tree-optimization/64909] [4.8 " rguenth at gcc dot gnu.org
2015-04-07 13:41 ` rguenth at gcc dot gnu.org
2015-06-23  8:59 ` 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-64909-4-uaNLJXBKyg@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).