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/101248] [AVX512] The upper bits of FIXUPIMMS{S,D} should come from src1 not dest. Date: Wed, 30 Jun 2021 01:08:13 +0000 [thread overview] Message-ID: <bug-101248-4-JmdcTG9soQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101248-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101248 --- Comment #3 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:ed392e9db434898eccec81edd85323d21d555fe9 commit r12-1923-ged392e9db434898eccec81edd85323d21d555fe9 Author: liuhongt <hongtao.liu@intel.com> Date: Mon Jun 28 19:27:23 2021 +0800 The upper bits of FIXUPIMMS{S,D} should come from src1 not dest. gcc/ChangeLog: PR target/101248 * config/i386/sse.md (avx512f_sfixupimm<mode><sd_maskz_name><round_saeonly_name>): Refined to .. (avx512f_sfixupimm<mode><maskz_scalar_name><round_saeonly_name>): this. (avx512f_sfixupimm<mode>_mask<round_saeonly_name>"): Refined. * config/i386/subst.md (maskz_scalar): New define_subst. (maskz_scalar_name): New subst_attr. (maskz_scalar_op5): Ditto. (round_saeonly_maskz_scalar_op5): Ditto. (round_saeonly_maskz_scalar_operand5): Ditto. gcc/testsuite/ChangeLog PR target/101248 * gcc.target/i386/pr101248.c: New test.
next prev parent reply other threads:[~2021-06-30 1:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-29 2:09 [Bug target/101248] New: " crazylht at gmail dot com 2021-06-29 2:12 ` [Bug target/101248] " crazylht at gmail dot com 2021-06-29 2:14 ` crazylht at gmail dot com 2021-06-30 1:08 ` cvs-commit at gcc dot gnu.org [this message] 2021-06-30 1:14 ` 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-101248-4-JmdcTG9soQ@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).