public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104946] [12 regression] Suboptimal gimple foding for blendvpd under sse4.1 Date: Wed, 16 Mar 2022 08:57:04 +0000 [thread overview] Message-ID: <bug-104946-4-eWEEsjpb0A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104946-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104946 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:570d5bff9af537265a3e0935140786e5fdf51de1 commit r12-7662-g570d5bff9af537265a3e0935140786e5fdf51de1 Author: liuhongt <hongtao.liu@intel.com> Date: Wed Mar 16 15:59:57 2022 +0800 Don't fold __builtin_ia32_blendvpd w/o sse4.2. __builtin_ia32_blendvpd is defined under sse4.1 and gimple folded to ((v2di) c) < 0 ? b : a where vec_cmpv2di is under sse4.2 w/o which it's veclowered to scalar operations and not combined back in rtl. gcc/ChangeLog: PR target/104946 * config/i386/i386-builtin.def (BDESC): Add CODE_FOR_sse4_1_blendvpd for IX86_BUILTIN_BLENDVPD. * config/i386/i386.cc (ix86_gimple_fold_builtin): Don't fold __builtin_ia32_blendvpd w/o sse4.2 gcc/testsuite/ChangeLog: * gcc.target/i386/sse4_1-blendvpd-1.c: New test.
next prev parent reply other threads:[~2022-03-16 8:57 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-16 5:54 [Bug target/104946] New: " crazylht at gmail dot com 2022-03-16 5:58 ` [Bug target/104946] " crazylht at gmail dot com 2022-03-16 7:53 ` rguenth at gcc dot gnu.org 2022-03-16 8:57 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-16 9:00 ` crazylht 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-104946-4-eWEEsjpb0A@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).