public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "liuhongt at gcc dot gnu.org" <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, 18 Dec 2023 09:27:26 +0000 [thread overview] Message-ID: <bug-104401-4-vD2Z7pBGhu@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 Hongtao Liu <liuhongt at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |liuhongt at gcc dot gnu.org --- Comment #6 from Hongtao Liu <liuhongt at gcc dot gnu.org> --- On latest trunk, we have 19 <bb 2> [local count: 1073741824]: 20 _6 = VIEW_CONVERT_EXPR<vector(4) int>(value_2(D)); 21 _7 = VIEW_CONVERT_EXPR<vector(4) int>(input_3(D)); 22 _8 = _6 < _7; 23 _4 = VEC_COND_EXPR <_8, _6, _7>; 24 _5 = VIEW_CONVERT_EXPR<vector(2) long long int>(_4); 25 return _5; 26 27} And we can match a < b ? a : b for vector modes.
next prev parent reply other threads:[~2023-12-18 9:27 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 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 [this message] 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-vD2Z7pBGhu@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: linkBe 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).