public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104401] [x86] Failure to recognize min/max pattern using pcmp+pblendv
Date: Mon, 07 Feb 2022 06:51:27 +0000	[thread overview]
Message-ID: <bug-104401-4-LmrxnIqatL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104401-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> (set (reg:V16QI 93)
>     (unspec:V16QI [
>             (subreg:V16QI (reg/v:V2DI 92 [ input ]) 0)
>             (subreg:V16QI (reg/v:V2DI 91 [ value ]) 0)
>             (subreg:V16QI (gt:V4SI (subreg:V4SI (reg/v:V2DI 92 [ input ]) 0)
>                     (subreg:V4SI (reg/v:V2DI 91 [ value ]) 0)) 0)
>         ] UNSPEC_BLENDV))
> 
> blend uses unspec which makes this a little harder

I think it could be done in gimple level.

 18  _10 = VIEW_CONVERT_EXPR<vector(4) int>(value_2(D));
 19  _11 = VIEW_CONVERT_EXPR<vector(4) int>(input_3(D));
 20  _12 = _10 < _11;
 21  _13 = VIEW_CONVERT_EXPR<vector(4) int>(_12);
 22  _5 = VIEW_CONVERT_EXPR<vector(16) char>(_13);
 23  _4 = VIEW_CONVERT_EXPR<vector(16) char>(value_2(D));
 24  _6 = VIEW_CONVERT_EXPR<vector(16) char>(input_3(D));
 25  _8 = .VCOND (_5, { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }, _4,
_6, 108);
 26  _9 = VIEW_CONVERT_EXPR<__m128i>(_8);

  parent reply	other threads:[~2022-02-07  6:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 21:32 [Bug target/104401] New: " gabravier at gmail dot com
2022-02-05 23:25 ` [Bug target/104401] " pinskia at gcc dot gnu.org
2022-02-05 23:28 ` pinskia at gcc dot gnu.org
2022-02-07  6:51 ` crazylht at gmail dot com [this message]
2022-02-07  6:57 ` pinskia at gcc dot gnu.org
2022-02-07  7:11 ` crazylht at gmail dot com
2022-02-07  7:59 ` rguenth at gcc dot gnu.org
2023-12-18  9:27 ` liuhongt at gcc dot gnu.org
2024-01-11  1:20 ` cvs-commit at gcc dot gnu.org
2024-01-11  1:21 ` liuhongt at gcc dot gnu.org
2024-01-20 17:18 ` 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-104401-4-LmrxnIqatL@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).