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 target/98167] [x86] Failure to optimize operation on indentically shuffled operands into a shuffle of the result of the operation
Date: Mon, 07 Dec 2020 12:26:49 +0000	[thread overview]
Message-ID: <bug-98167-4-31t0lnankK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98167-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
That works only for single-operation and doesn't really scale.  I think we want
to expose the permutes at the GIMPLE level via ix86_gimple_fold_builtin.  We
already handle IX86_BUILTIN_SHUFPD there but not IX86_BUILTIN_SHUFPS for
some reason.

  parent reply	other threads:[~2020-12-07 12:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07  2:09 [Bug target/98167] New: [x86] Failure to optimize operation on indentically shuffled operand " gabravier at gmail dot com
2020-12-07  2:12 ` [Bug target/98167] [x86] Failure to optimize operation on indentically shuffled operands " gabravier at gmail dot com
2020-12-07  8:04 ` rguenth at gcc dot gnu.org
2020-12-07 12:19 ` crazylht at gmail dot com
2020-12-07 12:26 ` rguenth at gcc dot gnu.org [this message]
2020-12-07 12:39 ` rguenth at gcc dot gnu.org
2020-12-07 12:40 ` rguenth at gcc dot gnu.org
2020-12-07 12:43 ` rguenth at gcc dot gnu.org
2020-12-08 23:05 ` glisse at gcc dot gnu.org
2020-12-10  5:49 ` crazylht at gmail dot com
2021-01-14 10:45 ` crazylht at gmail dot com
2021-01-14 10:59 ` jakub at gcc dot gnu.org
2021-08-27  0:51 ` cvs-commit at gcc dot gnu.org
2021-08-27  0:58 ` crazylht at gmail dot com
2021-08-27  1:13 ` pinskia at gcc dot gnu.org
2021-08-27  5:48 ` crazylht at gmail dot com
2021-08-27  6:31 ` crazylht at gmail dot com
2021-08-27  6:48 ` pinskia at gcc dot gnu.org
2021-08-27  7:02 ` crazylht at gmail dot com
2021-08-27  7:39 ` pinskia at gcc dot gnu.org
2022-01-11 11:27 ` rguenth at gcc dot gnu.org
2022-11-15  5:36 ` cvs-commit 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-98167-4-31t0lnankK@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).