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/114908] fails to optimize avx2 in-register permute written with std::experimental::simd
Date: Mon, 06 May 2024 09:05:05 +0000	[thread overview]
Message-ID: <bug-114908-4-nvHAEhaINt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114908-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Matthias Kretz (Vir) <mkretz at gcc dot gnu.org> ---
The stdx::simd implementation in this area is old and mainly tuned to be
correct. I can rewrite the split and concat implementation to use
__builtin_shufflevector (which wasn't available in GCC at the time when I
originally implemented it). Doing so I can resolve this issue.

How do you want to handle this? Because it would certainly be nice if the
compiler can optimize this in the same way as Clang can. Should I try to come
up with a testcase that doesn't need stdx::simd and then improve stdx::simd
independently?

  parent reply	other threads:[~2024-05-06  9:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 16:05 [Bug target/114908] New: " lee.imple at gmail dot com
2024-05-01 17:21 ` [Bug target/114908] " pinskia at gcc dot gnu.org
2024-05-01 17:31 ` [Bug tree-optimization/114908] " pinskia at gcc dot gnu.org
2024-05-02 11:12 ` rguenth at gcc dot gnu.org
2024-05-06  9:05 ` mkretz at gcc dot gnu.org [this message]
2024-05-06  9:16 ` rguenther at suse dot de
2024-05-06 10:00 ` mkretz at gcc dot gnu.org
2024-05-06 10:12 ` rguenth at gcc dot gnu.org
2024-05-06 10:30 ` mkretz at gcc dot gnu.org
2024-05-07  3:09 ` lee.imple at gmail dot com

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-114908-4-nvHAEhaINt@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).