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/110788] Spilling to mask register for GPR vec_duplicate Date: Fri, 28 Jul 2023 02:07:11 +0000 [thread overview] Message-ID: <bug-110788-4-T2PB0NQTg2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110788-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110788 --- Comment #5 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:54e54f77c1012ab53126314181c51eaee146ad5d commit r14-2833-g54e54f77c1012ab53126314181c51eaee146ad5d Author: liuhongt <hongtao.liu@intel.com> Date: Thu Jul 27 15:14:39 2023 +0800 Add UNSPEC_MASKOP to vpbroadcastm pattern. Prevent rtl optimization of vec_duplicate + zero_extend to vpbroadcastm since there could be an extra kmov after RA. gcc/ChangeLog: PR target/110788 * config/i386/sse.md (avx512cd_maskb_vec_dup<mode>): Add UNSPEC_MASKOP. (avx512cd_maskw_vec_dup<mode>): Ditto. gcc/testsuite/ChangeLog: * gcc.target/i386/pr110788.c: New test.
next prev parent reply other threads:[~2023-07-28 2:07 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-24 8:40 [Bug target/110788] New: " rguenth at gcc dot gnu.org 2023-07-27 7:02 ` [Bug target/110788] " crazylht at gmail dot com 2023-07-27 7:09 ` crazylht at gmail dot com 2023-07-27 11:29 ` ubizjak at gmail dot com 2023-07-27 13:55 ` crazylht at gmail dot com 2023-07-28 2:07 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-28 2:30 ` crazylht at gmail dot com 2023-11-30 10:51 ` liuhongt 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-110788-4-T2PB0NQTg2@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).