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/111133] SLP of scatters not implemented
Date: Wed, 08 Nov 2023 12:17:27 +0000	[thread overview]
Message-ID: <bug-111133-4-Zp4613XaiZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111133-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-11-08
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
With

#pragma GCC ivdep

the dependence issue is gone but we are not grouping gathers/scatters in
vect_analyze_data_ref_accesses.  Technically those are not "groups",
we wouldn't know how to set gap/size.

So to SLP scatters we'd need to optimistically perform SLP discovery on
"all" of them (or likely more successful, start greedy discovery from
the offset or the stored data side, aka from loads).  Eventually handled
when SLP discovery is rewritten.

For now priority #1 is to get single-lane discovery work for scatters.

  reply	other threads:[~2023-11-08 12:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 13:10 [Bug tree-optimization/111133] New: " rguenth at gcc dot gnu.org
2023-11-08 12:17 ` rguenth at gcc dot gnu.org [this message]
2023-11-09 12:59 ` [Bug tree-optimization/111133] " cvs-commit at gcc dot gnu.org
2023-11-09 13:00 ` [Bug tree-optimization/111133] multi-lane " 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-111133-4-Zp4613XaiZ@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).