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/52252] An opportunity for x86 gcc vectorizer (gain up to 3 times)
Date: Thu, 31 Aug 2023 07:07:48 +0000	[thread overview]
Message-ID: <bug-52252-4-A1kBeSVjRY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52252-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
We are not optimally vectorizing this yet, we are using SLP to cover
out[0], out[1], out[2] and single element interleaving for out[3].  The
stores end up strided (aka scalar), that's not what the reporter intended.
We also unroll the loop four times.

The SLP discovery code splits the store group (in the end we should avoid
throwing away such information).  This makes it have a gap and stores with
a gap are only supported "strided" (we could at least store two and one
element, but ...).  We don't support "merging" back the group from SLP
and non-SLP.  With SLP only we might recover here, possibly we shouldn't
allow half SLP / non-SLP for a store group but it might fail even after
discovery so it might be difficult to force this.  Maybe a good case to
"prime" single-lane SLP.

  parent reply	other threads:[~2023-08-31  7:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 22:42 [Bug c/52252] New: " evstupac at gmail dot com
2012-02-15 11:55 ` [Bug tree-optimization/52252] " rguenth at gcc dot gnu.org
2012-02-29 12:34 ` evstupac at gmail dot com
2012-07-13  8:48 ` rguenth at gcc dot gnu.org
2014-02-11 14:27 ` evstupac at gmail dot com
2014-05-07 12:11 ` kyukhin at gcc dot gnu.org
2014-06-11  8:38 ` kyukhin at gcc dot gnu.org
2014-06-18  7:47 ` kyukhin at gcc dot gnu.org
2023-08-31  7:07 ` rguenth at gcc dot gnu.org [this message]
2023-11-28  6:06 ` pinskia at gcc dot gnu.org
2023-11-28 10:55 ` rguenther at suse dot de
2023-11-28 22:24 ` pinskia 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-52252-4-A1kBeSVjRY@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).