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/96912] Failure to optimize pblendvb pattern
Date: Thu, 03 Sep 2020 08:03:05 +0000	[thread overview]
Message-ID: <bug-96912-4-suw607uphK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96912-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2020-09-03
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
On GIMPLE this could be pattern-matched to a VEC_PERM_EXPR <> which is
how to represent blends.  Of course matching this on RTL is possible as well.

The difficulty is of course the mismatch in element sizes where the
mask appears to be byte granular while the data to be blended is double-words.

  reply	other threads:[~2020-09-03  8:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03  7:31 [Bug tree-optimization/96912] New: Failure to optimize pattern gabravier at gmail dot com
2020-09-03  8:03 ` rguenth at gcc dot gnu.org [this message]
2020-09-03  8:03 ` [Bug tree-optimization/96912] Failure to optimize pblendvb pattern glisse at gcc dot gnu.org
2020-11-24 18:07 ` jakub at gcc dot gnu.org
2021-08-15  0: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-96912-4-suw607uphK@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).