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/104978] [avx512fp16] wrong code for _mm_mask_fcmadd_round_sch Date: Tue, 22 Mar 2022 03:48:58 +0000 [thread overview] Message-ID: <bug-104978-4-1PWkWjnTcd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104978-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104978 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Hongyu Wang <hongyuw@gcc.gnu.org>: https://gcc.gnu.org/g:7bce0be03b857eefe5990c3ef0af06ea8f8ae04e commit r12-7747-g7bce0be03b857eefe5990c3ef0af06ea8f8ae04e Author: Hongyu Wang <hongyu.wang@intel.com> Date: Sat Mar 19 01:16:29 2022 +0800 AVX512FP16: Fix wrong code for _mm_mask_f[c]madd.*sch [PR 104978] For complex scalar intrinsic like _mm_mask_fcmadd_sch, the mask should be and by 1 to ensure the mask is bind to lowest byte. Use masked vmovss to perform same operation which omits higher bits of mask. gcc/ChangeLog: PR target/104978 * config/i386/sse.md (avx512fp16_fmaddcsh_v8hf_mask1<round_expand_name): Use avx512f_movsf_mask instead of vmovaps or vblend, and force_reg before lowpart_subreg. (avx512fp16_fcmaddcsh_v8hf_mask1<round_expand_name): Likewise. gcc/testsuite/ChangeLog: PR target/104978 * gcc.target/i386/avx512fp16-vfcmaddcsh-1a.c: Adjust asm scan. * gcc.target/i386/avx512fp16-vfmaddcsh-1a.c: Ditto. * gcc.target/i386/avx512fp16-vfcmaddcsh-1c.c: Removed. * gcc.target/i386/avx512fp16-vfmaddcsh-1c.c: Ditto. * gcc.target/i386/pr104978.c: New test.
next prev parent reply other threads:[~2022-03-22 3:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-18 12:21 [Bug target/104978] New: " crazylht at gmail dot com 2022-03-18 12:37 ` [Bug target/104978] " crazylht at gmail dot com 2022-03-18 12:52 ` crazylht at gmail dot com 2022-03-18 12:57 ` crazylht at gmail dot com 2022-03-22 3:48 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-22 3:49 ` wwwhhhyyy333 at gmail dot com 2022-03-22 9:41 ` 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-104978-4-1PWkWjnTcd@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).