public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mkretz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114966] fails to optimize avx2 in-register permute written with std::experimental::simd
Date: Tue, 07 May 2024 07:08:20 +0000	[thread overview]
Message-ID: <bug-114966-4-j4XGEyjT0E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114966-4@http.gcc.gnu.org/bugzilla/>

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

Matthias Kretz (Vir) <mkretz at gcc dot gnu.org> changed:

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

--- Comment #2 from Matthias Kretz (Vir) <mkretz at gcc dot gnu.org> ---
GCC trunk recognizes a list-init of the vector builtin as a VEC_PERM_EXPR.
That's what's behind the generator ctor of simd. So something goes wrong there.
I had a quick look through the tree passes on compiler-explorer, and on
forwprop3 GCC 13 matches the VEC_PERM_EXPR, while trunk doesn't
(https://godbolt.org/z/9Pef3c9d9)

  parent reply	other threads:[~2024-05-07  7:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07  2:57 [Bug tree-optimization/114966] New: " lee.imple at gmail dot com
2024-05-07  3:18 ` [Bug tree-optimization/114966] " lee.imple at gmail dot com
2024-05-07  7:08 ` mkretz at gcc dot gnu.org [this message]
2024-05-07  8:58 ` rguenth at gcc dot gnu.org
2024-05-07 10:28 ` mkretz 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-114966-4-j4XGEyjT0E@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).