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/101471] AVX512 incorrect writemask generated for _mm512_fpclass_ps_mask in O0 Date: Wed, 25 Aug 2021 07:15:31 +0000 [thread overview] Message-ID: <bug-101471-4-Y5LKdFbFdp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101471-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101471 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:6604b336517463f9189e1c95db405a154aa7c815 commit r11-8924-g6604b336517463f9189e1c95db405a154aa7c815 Author: konglin1 <lingling.kong@intel.com> Date: Mon Aug 9 10:58:24 2021 +0800 i386: Fix _mm512_fpclass_ps_mask in O0 [PR 101471] gcc/ChangeLog: PR target/101471 * config/i386/avx512dqintrin.h (_mm512_fpclass_ps_mask): Fix macro define in O0. (_mm512_mask_fpclass_ps_mask): Ditto. gcc/testsuite/ChangeLog: PR target/101471 * gcc.target/i386/avx512f-pr101471.c: New test.
next prev parent reply other threads:[~2021-08-25 7:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-16 12:15 [Bug target/101471] New: " kastianoza at gmail dot com 2021-07-16 12:17 ` [Bug target/101471] " kastianoza at gmail dot com 2021-07-20 3:14 ` crazylht at gmail dot com 2021-07-20 3:15 ` crazylht at gmail dot com 2021-08-25 6:42 ` cvs-commit at gcc dot gnu.org 2021-08-25 7:15 ` cvs-commit at gcc dot gnu.org [this message] 2021-08-25 7:16 ` cvs-commit at gcc dot gnu.org 2021-08-25 7:17 ` cvs-commit at gcc dot gnu.org 2021-08-25 7:18 ` crazylht at gmail dot com 2023-11-30 9:04 ` 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-101471-4-Y5LKdFbFdp@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).